HKSM

A facilitated workshop used early in a Scrum initiative to align sponsors, the Product Owner, the Scrum Master, stakeholders, and potential team representatives on the product's purpose, target users, and value. It produces a concise Project Vision Statement plus initial assumptions, constraints, and high-level risks to guide backlog creation and release planning.

Key Points

• Held during initiation to shape a shared understanding of why the product exists and whom it serves.
• Facilitated by the Scrum Master; the Product Owner articulates desired outcomes and value.
• Focuses on business value, customer needs, success criteria, and boundaries, not detailed solutions.
• Produces a Project Vision Statement and captures high-level risks, assumptions, and constraints.
• Aligns stakeholders and sets direction for creating epics and the initial product backlog.
• Provides guardrails for release planning and future trade-off decisions.

Purpose of Analysis

The meeting analyzes the business need, target users, and expected benefits to ensure the product direction aligns with organizational strategy. Attendees assess assumptions, constraints, dependencies, and high-level risks to shape a realistic and value-focused vision.

By clarifying success measures and boundaries, the group creates a single source of truth that guides backlog refinement and release planning while reducing misalignment and scope drift.

Method Steps

1. Prepare and invite: Sponsor, Product Owner, Scrum Master, key stakeholders, and potential Scrum Team representatives.
2. Present context: Business case, problem/opportunity, strategic goals, and market insights.
3. Explore users and value: Discuss customer segments, personas, pain points, and desired outcomes.
4. Outline scope at a high level: Identify themes and epics without committing to detailed solutions.
5. Elicit constraints and risks: Capture assumptions, dependencies, regulations, budgets, and timelines.
6. Define success: Agree on measurable benefits, value metrics, and acceptance of project boundaries.
7. Draft the Project Vision Statement: Create a concise, 1-page narrative or elevator statement.
8. Validate and agree: Confirm shared understanding, record decisions, and document next steps for backlog creation and release planning.

Inputs Needed

• Business case or problem statement.
• Organizational strategy, product or portfolio goals.
• Market research, user insights, and competitor analysis.
• Known constraints: budget ranges, deadlines, compliance or regulatory needs.
• Technology considerations and existing product context or analytics.
• Stakeholder maps and any known dependencies.

Outputs Produced

• Project Vision Statement that expresses purpose, target users, and intended value.
• List of high-level epics or themes to seed the initial product backlog.
• Documented assumptions, constraints, dependencies, and high-level risks.
• Agreed success criteria and value measures to guide prioritization.
• Stakeholder alignment and recorded decisions for traceability.

Interpretation Tips

• Keep the vision short, memorable, and value-focused so it is easy to communicate.
• Treat it as stable guidance but allow updates when strategy or market conditions change.
• Use the vision to filter backlog items: if a story does not support the vision, challenge it.
• Link success criteria to measurable outcomes to support empirical inspection and adaptation.
• Ensure risks and constraints inform release planning and DoR considerations.

Example

A company plans a new customer self-service portal. In the Project Vision Meeting, the Product Owner explains the goal to reduce support calls by 30 percent and improve customer satisfaction. Stakeholders identify primary user personas, key epics like account management and knowledge search, a regulatory constraint for data retention, and a budget window for the first release. The team drafts a 1-page vision and agrees on value metrics to guide the initial backlog.

Pitfalls

• Turning the session into detailed solution design instead of articulating value and outcomes.
• Missing critical stakeholders, resulting in rework and conflicting expectations later.
• Creating an overly long, vague, or jargon-heavy vision that is hard to apply.
• Skipping measurable success criteria, which weakens prioritization and validation.
• Ignoring constraints and risks, leading to unrealistic plans and surprise delays.

PMP/SCRUM Example Question

A Scrum team is initiating a new product. Which artifact is the primary outcome of the Project Vision Meeting?

1. Business case
2. Product roadmap
3. Project Vision Statement
4. Sprint Goal

Correct Answer: C — Project Vision Statement

Explanation: The Project Vision Meeting produces a concise Project Vision Statement to guide backlog creation and release planning. The business case may inform the meeting, the roadmap comes later, and Sprint Goals are set per sprint.