Half of the value of plans is in the process one goes
through to produce them.
Planning can occur during any phase.
Plans must be regularly maintained because they will
otherwise quickly go obsolete.
To minimize maintenance costs, the volatile organization
chart, project schedule, and work breakdown structure are
developed and maintained as separate documents.
The management plan has traditionally gone by numerous
other names:
Project plan, which is too restrictive. What about
management plans for programs of related projects?
Software development plan (SDP), which is too also too
restrictive. What about plans for the reengineering of
businesses, the development of systems, or the development
of reusable intellectual property. The term system
development plan is also too restrictive for the same
reasons.
The previous terms are also too general, because they
imply the inclusion of planning information that is often
best relegated to separated planning documents.
Use the procedure in the associated work flow to produce
this work product.
If you tailor this work product, then tailor its
associated standard, template, and inspection checklist.