HKSM
Project Vision Meeting
A Project Vision Meeting brings together the Program Business Stakeholder(s), Program Product Owner, Program Scrum Master, and Chief Product Owner to surface the business environment, key requirements, and stakeholder expectations, culminating in a clear, shared Project Vision Statement.
Key Points
- Attendees typically include Program Business Stakeholder(s), Program Product Owner, Program Scrum Master, and the Chief Product Owner.
- Focuses on clarifying business context, high-level requirements, and success expectations.
- Usually held early in initiation and revisited when strategy, market, or scope shifts occur.
- Primary output is a concise Project Vision Statement that guides planning, prioritization, and communication.
Example
For a new mobile banking app, the team convenes a Project Vision Meeting with executives, compliance, the Program PO, the Program SM, and the Chief PO. They agree on target users, regulatory constraints, business outcomes (e.g., increase mobile adoption by 25%), and the MVP focus. The session produces a one-page vision statement that becomes the north star for backlog creation and stakeholder communications.
PMP Example Question
Which statement best describes the main purpose of a Project Vision Meeting?
- To create the detailed sprint task list for the first iteration.
- To align key stakeholders on business context, high-level needs, and expectations to craft a Project Vision Statement.
- To approve the final product release and close the project.
- To conduct a quantitative risk analysis and build response plans.
Correct Answer: B — Align stakeholders to define a clear project vision
Explanation: The Project Vision Meeting is about establishing shared understanding of context, needs, and expectations that produce a guiding vision statement; it is not for detailed task planning, release approval, or risk quantification.
