|
4.2 Develop Project Management Plan The process of documenting the actions necessary to define, prepare, integrate, and coordinate all subsidiary plans Simple Version: Create a document that explains how the project will be managed. Include how the project will be executed, monitored controlled and closed. The PMBOK acknowledges that the plan is “refined until closure”, this is a living document, and uses the term “progressive elaboration” to describe the ongoing nature of the updates. This term and idea might be useful for defending the inevitable updates to the project than. | |
|
PMI |
Agile PMBOK, Agile Difference, Comment |
|
Inputs Project Charter Outputs from planning processes Enterprise Environmental Factors (Govt standards, organizational infrastructure, marketplace conditions) Organizational Process Assets (standards, templates, Lessons Learned notes) Tools and Techniques Expert Judgement Outputs Project Management Plan |
Inputs Project Charter / Vision Outputs from planning processes – Candidate Features / Stories Enterprise Environmental Factors (Govt standards, organizational infrastructure, marketplace conditions) Organizational Process Assets (standards, templates, Lessons Learned notes) Tools and Techniques Expert Judgement Outputs Project Management Plan In an agile environment we can still develop and document a project management plan, however for small projects the documentation associated with this step might be small. Fortunately the PMBOK recommends that this process follow Progressive Elaboration – i.e. our plans are updated and refined as the project progresses, so this fits nicely with agile’s iterative planning concepts. |
4.2 Develop Project Management Plan