Picture a team of twenty people working hard, but each one imagining a slightly different product. The result is wasted effort and conflicting decisions. A shared vision is the single picture everyone holds of the end result: what will change for the user or the organization when the project succeeds? On the PMP exam, the project manager is expected to make sure this vision exists and that everyone understands it the same way.
The tool for this is a vision statement: one or two short sentences describing who benefits, what their problem is, and what value they will get. A good one sounds like: "Patients book an appointment and see their waiting time from their phone in under a minute." Notice it names no technology and no plan, only the purpose. It is written together with the sponsor, the product owner, and the team, not alone in the PM's office, because people commit to what they helped create.
The vision answers "why"; the team charter and working agreements you met earlier answer "how we work together". The key exam point is that the team sets and agrees its own ground rules, and the PM facilitates the session rather than imposing the rules. When someone breaks an agreed rule, the first step is to remind them of it and refer back to the charter, not to punish or escalate.
A vision written on day one and then forgotten is worth nothing. Keep it alive: show it at the start of every planning session, link each task or user story to the goal it serves, and go back to it when people disagree about priorities. In agile teams the product owner owns the product vision and sets a sprint goal for each sprint that moves the team one step closer to it. If the market or the organization's needs change, the vision is updated openly with everyone instead of the direction drifting silently.
💡 Key points
- A vision statement is short and describes the beneficiary and the value, not the technology or the plan.
- Build the vision together with the sponsor and the team; involvement creates commitment.
- The team sets its own ground rules; the PM facilitates rather than imposes.
- Keep the vision alive: link work to it, return to it in disagreements, and update it openly.
🌍 Real-life example
A bank in Casablanca is launching a new mobile app. In week one, the PM brought the sponsor, the product owner, and the developers into a two-hour workshop, and they came out with a vision statement: "A young customer opens an account from their phone in ten minutes without visiting a branch." They pinned it on the team board, and every sprint began with the question: how does this goal get us closer to the ten minutes? When marketing asked for a mini-game inside the app, the team went back to the vision and the product owner calmly deferred it, because it doesn't serve the goal right now.
📖 Key terms
| English | العربية |
|---|---|
| Shared Vision | الرؤية المشتركة |
| Vision Statement | بيان الرؤية |
| Product Vision | رؤية المنتج |
| Sprint Goal | هدف السبرنت |
| Ground Rules | القواعد الأساسية |
| Working Agreements | اتفاقيات العمل |