4.7. Direct to Blueprint

The goal of software planning is to get a blueprint to the developers. In order to avoid inefficient communications, it is important to move information from the business expert to the blueprint as quickly and directly as possible. As in any other communications exercise, the more often that a message must be translated and transcribed, the more likely that errors and inefficiencies are introduced.

Direct to Blueprint describes a planning process that moves information as directly and efficiently as possible from the client business expert to the final blueprint format.

When gathering documents, the earlier that you can get essential information into the blueprint, the better. Resist the tendency to produce a “standard ...

Get Planning Smarter: Creating Blueprint-Quality Software Specifications now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.