My Bf Wants To See My Boobs

The never-ending design

Often I experience project situations where very exporting concepts (technical concept and business concept) are available. In almost endless Work were specified page after page. This certainly has its advantages: the customer feels safe and knows what he gets in the end. Also can be estimated relatively accurately on the basis of the present specification, what the costs and risks for implementation are.

But so detailed are the concepts also appear somewhere during the implementation always will be questions and there are some very pragmatic advice on how the project can deal with such situations:

first Read concept (business and technical concept)
I have often had discussions with developers about concepts that really were not necessary if one views would cast a glance into the business approach. This does not mean that the developer has to read at the beginning of the project over 1000 pages concept. But he do if he receives a work package, at least read this part of the concept that are relevant to the AP. This includes the business concept. Often this is forgotten during development.

second The conversation looking
Whether a developer or project manager: When questions arise in a concept, one should immediately resolve this in an interview. Easy to make assumptions is also faster, yes, but not necessarily purposeful, especially if the assumption was wrong. Ideally speaking First, the developer with the project. This can at best help already. If this is not the case, should the project manager to demand an appropriate meeting.
Open questions should be discussed with appropriate preparation by project management / development and a concept proposal with the customer and then in a log, or weekly report be noted. This can be traced at a later date.

third complementary approach with missing elements.
If indeed missing parts specifications, these should be added. Usually there until the end of a project and probably beyond repeatedly elements that should be added in one concept. A concept lives during a project and should not be sacrosanct. Based on the discussion with the customer, a concept also be amended from time, especially when it recommended from a technical point of view. The situation of the project but must assess the situation and act accordingly.