There are situations when a standard is called out in a contract that stipulates the outline and contents of a Software
Development Plan. In this case, you would use that instead of the proposed outline shown in the HTML template, but you
should form a clear mapping of the information requirements of that standard to the outline in the template provided.
Good software development plans evolve. A useful Software Development Plan is periodically updated (it is not stagnant
shelfware), and it is understood and embraced by managers and practitioners.
The Software Development Plan is the defining document for the project's process. Prepare a single Software Development
complies with organizational standards for content
complies with the contract (if any)
provides traceability to, or waivers from, contract and organization requirements
is updated at each major milestone
evolves along with the design and requirements
A standard format promotes:
reuse of processes, methods, experience, and people
accountability for organizational expectations
homogeneous process objectives
A key discriminator of a good Software Development Plan is its conciseness, lack of philosophy, and focus on meaningful
standards and procedures.