A PgMP aspirant recently asked me a deceptively simple question:
“Should the Program Roadmap be developed only after the Program Charter is approved?”
My answer was:
Not necessarily.
And this is where understanding program management as a practitioner becomes more important than memorizing a sequence of documents.
At first glance, the sequence appears straightforward:
Business Case → Program Charter → Program Roadmap → Program Management Plan
After all, the Program Charter formally authorizes the program. So why would we develop a roadmap for a program that hasn’t even been authorized yet?
Good question.
But the reality is more nuanced.
What does the PMI Standard tell us?
The Standard for Program Management, Fifth Edition establishes an important sequence.
The business case comes first and provides the justification for the investment. Following approval of the business case, the Program Charter is presented to the appropriate governance authority for approval, funding, and authorization.
And the Charter itself already contains quite a lot of high-level information.
It includes the program’s goals and objectives, benefits, dependencies, high-level risks, resources and, importantly for our discussion, the overall program timeline and key milestone dates.
The Standard then describes the Program Roadmap as a major component of the Program Management Plan. It graphically and chronologically represents the program’s intended direction, including major milestones, decision points, dependencies and the connection between organizational strategy and program work.
So it would be very easy to conclude:
“Fine. Charter gets approved first. Then I develop the Roadmap.”
But don’t stop there.
Because the PgMP Examination Content Outline (ECO) gives us another important clue.
The ECO changes how you should think about the sequence
Look carefully at Domain I: Strategic Program Alignment.
One of the tasks (task # 2) of the program manager is to:
Establish a high-level roadmap with milestones and preliminary estimates to obtain initial validation and approval from the executive sponsor.
The very next task (task # 3) further develops that high-level roadmap and financial framework as a baseline for program definition, planning and execution.
And later, the ECO expects (task # 09) the program manager to obtain organizational leadership approval by presenting the Program Charter with its high-level costs, milestone schedule and benefits.
That wording matters.
The high-level roadmap isn’t always something that magically appears after authorization.
Sometimes you need enough of a roadmap to make authorization possible.
Think of it as two levels of maturity
This is the distinction I want my PgMP learners to remember:
Pre-authorization: High-Level Roadmap
Strategic direction. Major milestones. Preliminary estimates. Major dependencies. Broad sequencing. Enough information for executives to understand:
“If we authorize this program, what does the journey roughly look like?”
Then comes:
Program Charter Approval
The governance authority formally authorizes the program and gives the program manager authority to proceed.
And after authorization:
Elaborated Program Roadmap
Now the roadmap can progressively mature as the program is planned, components become clearer, dependencies are better understood and the benefits realization path becomes more concrete.
This isn’t contradictory.
It is progressive elaboration at the program level.
In fact, the Standard itself recognizes that program formulation is not a neat document-by-document waterfall. During formulation, the sponsor, sponsoring organization and program manager work together on estimates of scope, resources and cost, initial high-level assessments, the Program Charter and milestones. The Charter then becomes the primary document used to decide whether the program should be authorized.
So don’t confuse formal authorization with the first time thinking about the program’s path.
Those are two very different things.
Now think like a PgMP exam candidate
Suppose you get this question:
A proposed strategic program involves several interdependent components and significant investment. The executive sponsor wants to understand major milestones, preliminary estimates and the expected path toward benefits before providing initial approval. What should the program manager develop?
Don’t choose the detailed Program Management Plan.
Don’t jump to the Program Master Schedule.
And don’t argue that a roadmap cannot exist because the Charter hasn’t yet been approved.
The best answer is:
Establish the high-level Program Roadmap.
Why?
Because the ECO explicitly associates the high-level roadmap, milestones and preliminary estimates with obtaining initial validation and approval from the executive sponsor.
Now change the question slightly:
Organizational leadership has reviewed the proposed program’s objectives, high-level costs, milestone schedule and expected benefits. What should the program manager seek next to formally initiate the program?
Now your answer shifts to:
Approval of the Program Charter.
Because authorization comes through the Charter.
That’s the kind of distinction the PgMP exam expects you to recognize.
The mentor’s takeaway
Don’t memorize this as:
Charter first. Roadmap second.
That’s too simplistic.
Instead, understand it this way:
A high-level roadmap can support the decision to authorize the Program Charter. After authorization, the roadmap is progressively elaborated and becomes an important part of planning and ongoing strategic alignment.
The Standard for Program Management itself says that during the Program Definition phase, the business case, Program Charter and Program Roadmap are formulated, and only after approval is the Program Management Plan prepared.
That one statement should make us cautious about treating these artifacts as a rigid waterfall.
Program management isn’t:
Finish Document A → lock it → create Document B → lock it → create Document C.
It’s an iterative process of turning strategic intent into an increasingly credible path toward benefits.
And sometimes, before an executive can say:
“I authorize this program.”
they first need to see:
“Show me how you believe we’re going to get there.”
That is where the high-level Program Roadmap becomes powerful.
PgMP Exam Lens
When you see initial validation, major milestones, preliminary estimates and executive sponsor approval, think:
High-Level Program Roadmap.
When you see formal authorization, authority to use organizational resources and authorization to initiate the program, think:
Program Charter.
When you see detailed integration of components, subsidiary plans and management controls, think:
Program Management Plan.
Understanding those boundaries will help you far more on the PgMP exam than memorizing a sequence.
To Your Success.
Leave a Reply