People · Topic 1 of 7
Developing a Common Vision
Learn how a project manager builds a shared vision across predictive, agile and hybrid projects, from the charter and objectives to team agreements.
- 5 min
- The sponsor and business case provide the reason for the project, and the project manager helps turn it into a vision the team shares.
- The project charter authorizes the project and records high level objectives, success criteria and the named project manager.
- In agile work, the product owner owns the product vision, and the product roadmap shows how it unfolds.
What it is
A common vision is a shared picture of what the project will achieve and why it matters. When every team member and stakeholder describes the outcome in roughly the same way, decisions get faster and arguments get smaller.
The project manager does not invent the vision alone. The sponsor and the business case supply the reason for the work, and the project manager helps the team and stakeholders turn that reason into goals everyone understands and accepts.
How it works
The vision has to be written down, tested with people and kept visible. A vision that lives only in the sponsor's head does not help a team that is deciding between two designs on a Tuesday afternoon.
Starting points in a predictive project
In a predictive (plan driven) project, the vision is captured early in the project charter. The charter is the document that formally authorizes the project and names the project manager. It usually holds the purpose, high level objectives, success criteria, summary milestones, a summary budget and the main assumptions and constraints.
The project manager reads the charter and the business case, then checks that the goals are specific enough to be measured. Vague goals such as "improve the customer experience" are turned into statements that a team can test, such as a target for a survey score or a drop in call volume.
Starting points in an agile project
In an agile (adaptive) project, the vision is often a short product vision statement owned by the product owner. A product roadmap then shows how the vision unfolds over releases. The team also writes a team charter or set of working agreements that describe how it will work together.
The project manager or agile coach helps the team ask simple questions. Who is the customer, what problem do we solve and what would make us call this a success?
Building agreement
The same activities work in every approach. They differ only in how formal they are.
| Activity | Purpose | Predictive example | Agile example |
|---|---|---|---|
| Kickoff meeting | Align everyone at the start | Formal kickoff with sponsor | Short launch session with the team |
| Vision workshop | Draw out different views | Facilitated charter review | Story mapping or roadmap session |
| Team charter | Agree on behavior | Ground rules and decision rights | Working agreements on the team board |
| Success criteria | Define done and value | Measurable objectives in the charter | Definition of done and sprint goals |
A workshop is useful because it exposes disagreement early. If two key stakeholders describe different outcomes, the project manager must resolve the gap before planning goes further.
Keeping the vision alive
The vision is revisited whenever conditions change. A new regulation, a merger or a failed assumption can all make the original statement out of date.
In a hybrid project (a mix of predictive and agile practices), the overall goals and constraints may stay fixed while the details are discovered iteratively. The project manager keeps the fixed parts stable and makes the flexible parts transparent.
Where this fits in the day to day
A common vision is an input to many other tasks. It helps when you rank scope, settle conflicts and explain a trade off to a stakeholder. If a request does not support the vision, that is a strong reason to question it.
When an exam scenario shows a team pulling in different directions, look for the answer that restates the goals with the group and checks for shared understanding before anything else.
What to remember for the exam
- The sponsor and business case provide the reason for the project, and the project manager helps turn it into a vision the team shares.
- The project charter authorizes the project and records high level objectives, success criteria and the named project manager.
- In agile work, the product owner owns the product vision, and the product roadmap shows how it unfolds.
- A team charter or working agreement defines how the team behaves, communicates and decides.
- Goals should be measurable, so vague wishes are turned into testable success criteria.
- A kickoff meeting and workshops are standard ways to align people at the start.
- Revisit the vision when assumptions, regulations or business priorities change.
- If stakeholders hold different pictures of the outcome, resolve this before planning or building continues.
Common mistakes
Treating the vision as a poster. A statement on a wall does nothing unless it is tied to objectives, decisions and priorities.
Letting the project manager write it alone. A vision imposed from above gets little commitment, so involve the team and key stakeholders.
Confusing vision with scope. The vision explains the outcome and the reason. Scope lists the work and deliverables needed to reach it.
Assuming agile projects need no vision. Agile teams need an even clearer goal, because they have fewer detailed plans to lean on.
Skipping alignment because the charter exists. A signed charter does not prove that people understand it the same way.
Do not start detailed planning while key stakeholders still disagree about the outcome, because every later plan will carry that disagreement forward.
Check yourself
Which document formally authorizes a predictive project and names the project manager?
The project charter.
Who owns the product vision on an agile project?
The product owner, who also keeps the roadmap in line with it.
Two senior stakeholders describe different project outcomes. What should the project manager do first?
Bring them together to clarify and agree the goals, then record the result in the charter or team agreements.
Topic 1 of 7 in People
Test yourself on People
The full PMI PMP question bank has 1,463 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by PMI. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.