HKSM

Company Mission is the organization’s stated purpose, target customers, and value promise that guides strategic choices. In SBOK-based Scrum projects, it serves as an enterprise input that steers the Product Vision, backlog prioritization, and release goals to ensure work advances the organization’s purpose.

Key Points

• Enterprise-level input that rarely changes during a project.
• Guides creation of the Product Vision and shapes epics, user stories, and release goals.
• Primarily used by the Product Owner for value-based prioritization and scope decisions.
• Referenced by the Scrum Master to facilitate alignment and resolve competing priorities.
• Acts as a decision filter when trade-offs arise among scope, schedule, cost, and quality.
• Links multiple SBOK processes, including Create Project Vision, Develop Epic(s), and Develop Prioritized Product Backlog.

Purpose

The mission ensures the product direction aligns with organizational purpose and strategic themes. It helps prevent waste by filtering out features that do not support the company’s reason for being.

By anchoring decisions to the mission, teams communicate consistent value to stakeholders and make coherent release and sprint goals.

Key Terms & Clauses

• Target customers and markets: who the organization serves.
• Value promise: the core benefit provided (e.g., affordability, security, convenience).
• Principles and constraints: ethics, compliance, safety, sustainability, and quality expectations.
• Strategic themes: high-level focus areas that guide what to build and what to avoid.
• Time horizon and stability: mission is enduring; strategies and tactics may change more frequently.

How to Develop/Evaluate

The mission is normally created by executive leadership and communicated as an organizational asset. If unclear to the Scrum Team, the Product Owner should seek clarification from sponsors or strategy leaders and document the interpretation as a project assumption.

Evaluate mission quality by checking: clarity on who is served and why, concise wording, decision usefulness, and alignment with current portfolio strategy. Red flags include vague language, conflicting directives, and lack of stakeholder endorsement.

How to Use

Use the mission as an input during SBOK processes and ceremonies to keep work aligned:

• Initiate - Create Project Vision: ensure the Project Vision Statement directly supports the company’s purpose.
• Plan - Develop Epic(s) and Develop Prioritized Product Backlog: tag items with mission-aligned themes; score or filter items by mission fit.
• Plan - Create Release Plan: set release goals that express mission outcomes (e.g., accessibility, security, customer reach).
• Implement - Backlog Refinement and Sprint Planning: use mission alignment as a tie-breaker when ordering stories and setting Sprint Goals.
• Review - Sprint Review: demonstrate how increments advance mission outcomes and customer value.
• Retrospect - Retrospect Sprint/Project: check for mission drift and adjust backlog or strategy with stakeholders.
• Scaling - Scrum of Scrums: synchronize cross-team work so all increments support the same mission themes.

Example Snippet

Sample mission: "We empower small businesses to grow by delivering secure, easy-to-use digital tools at a fair price."

Application: a Product Owner screens a proposed feature—advanced analytics behind a premium paywall. If "fair price" and "ease-of-use" are core, the team either rethinks pricing or simplifies the feature to keep it accessible, ensuring alignment with the mission.

Risks & Tips

• Risk of mission drift if backlog items are accepted due to short-term pressure; use a mission-fit check in the Definition of Ready.
• Vague mission statements cause inconsistent prioritization; ask for concrete examples and decision rules.
• Local optimization (team-level goals) can conflict with enterprise purpose; escalate conflicts to sponsors early.
• If the mission changes mid-project, reassess business justification, re-prioritize the backlog, and update release plans.
• Document mission assumptions in the Product Vision and communicate them during Sprint Reviews to maintain stakeholder alignment.

PMP/SCRUM Example Question

A Product Owner is preparing to prioritize epics and wants to ensure the backlog supports the organization’s purpose and target customers. Which input is most appropriate to guide these decisions?

1. Definition of Done.
2. Sprint Retrospective notes.
3. Team Working Agreement.
4. Company Mission.

Correct Answer: D — Company Mission

Explanation: The mission provides enterprise-level purpose and customer focus, making it the best input for alignment and prioritization. The other options are team-level or process-specific artifacts and do not express organizational purpose.