Deployment Baselines for Linear and Iterative Projects

The APM Body of Knowledge 7th edition introduced a new term deployment baseline and defined it as:

Deployment baseline:

Agreeing the integrated plan to enable managed deployment.

APM Body of Knowledge 7th edition

It’s a new phase for many many project managers, especially when applied to both linear and iterative lifecycles. So in this blog pose we are going to explore in a little more detail:

What is a deployment baseline?
What are the components of a deployment baseline for linear and iterative life cycles?
Compare and contrast the approaches to project baselines.
What is a deployment baseline?
A deployment baseline is simple the plan for the execution of the project. It supports the project management plan and typically sets out the baselines plans for the project. These normally include scope, timeline and budget. Although I prefer to add requirements to this as part of the scope. It’s important that these baselines be agreed for a number of reasons:

They provide an opportunity for senior management, the sponsor and steering group to review and sign off the plan. This reduced the risk of issues emerging later in the project or confusion about the actual commitment.
They form the basis of communication with other team members so they understand the planned work.
They help communicates to stakeholders such as users and operational staff the overall plan for the project. Without this communication, stakeholders can feel a bit left in the dark about want is happening.
The requirements form the basis of the expected performance for the system. Thys confirm what is going to be delivered and when.

For full detail: https://www.parallelprojecttraining.c...