HKSM

Large, high-level Product Backlog items that describe broad features or capabilities too big for a single sprint. In SBOK, epics are created early, prioritized for release planning, and later split into smaller user stories that can be estimated and delivered, keeping traceability to the original epic.

Key Points

• Represents a large requirement or feature that spans multiple sprints.
• Created during Initiate and recorded in the Prioritized Product Backlog.
• Used as input to release planning and refined during Groom Prioritized Product Backlog.
• Decomposed into user stories during planning before sprint commitment.
• Prioritized by the Product Owner based on value, risk, and dependencies.
• Maintains traceability from the epic to its child user stories and delivered increments.

Purpose

Epics provide a way to capture big ideas quickly so the team can align on scope and value without premature detail. They enable early prioritization and release planning, guiding where to invest effort as the product evolves.

As the product nears delivery of an epic, it is split into actionable user stories that can be estimated, planned into sprints, and validated incrementally.

Key Terms & Clauses

• Epic statement: As a [persona], I want [capability] so that [outcome].
• Business value: Why this epic matters and how it supports the product vision or release goal.
• Success criteria: High-level outcomes or metrics that indicate the epic delivered value.
• Constraints and non-functional needs: Performance, security, compliance, or platform boundaries to consider.
• Coarse estimate: T-shirt sizing (S/M/L/XL) or a rough range for planning purposes.
• Traceability ID: Links the epic to its user stories and to releases.

How to Develop/Evaluate

Start from the product vision and stakeholder inputs to draft clear, outcome-focused epic statements. Add brief context: key users, expected value, constraints, dependencies, and a coarse estimate suitable for release planning.

Evaluate priority using value, urgency, risk, and dependency impact. Review epics during Groom Prioritized Product Backlog; when an epic nears implementation, split it into INVEST-compliant user stories and validate acceptance boundaries with stakeholders.

How to Use

In SBOK, epics are produced in the Initiate process (Develop Epics) and become inputs to Create Prioritized Product Backlog and Conduct Release Planning. They guide high-level scope and sequencing across releases.

Later, during Plan and Estimate, epics feed Create User Stories for decomposition, Approve User Stories for validation, and Estimate/Commit User Stories for sprint readiness. Throughout execution, epics are refined in Groom Prioritized Product Backlog and closed when all child stories meet acceptance and are released.

Example Snippet

Epic: As a registered user, I want to manage my account so that I can keep my information up to date.

• Business value: Improves retention and reduces support requests.
• Constraint: Must comply with data privacy policies.
• Estimate: L (large). Traceability: EP-012.

Split into user stories (examples):

• As a user, I can update my contact details to keep them current. (Story ID: US-312, child of EP-012).
• As a user, I can change my password to maintain account security. (Story ID: US-313, child of EP-012).
• As a user, I can view recent login activity to detect suspicious access. (Story ID: US-314, child of EP-012).

Risks & Tips

• Risk: Pulling epics directly into a sprint leads to rollover and missed commitments. Tip: Split into stories before sprint planning.
• Risk: Over-detailing epics early wastes time if priorities change. Tip: Keep epics lightweight until they near delivery.
• Risk: Losing traceability from stories to epics obscures value tracking. Tip: Maintain IDs and linkage in the backlog tool.
• Risk: Ignoring constraints yields rework later. Tip: Capture key non-functional requirements at the epic level.
• Risk: Dependencies across teams stall progress. Tip: Highlight dependencies in release planning and coordinate via Scrum of Scrums if scaling.
• Risk: Stale epics no longer aligned with vision. Tip: Reassess priority and relevance during regular backlog grooming.

PMP/SCRUM Example Question

During Initiate, the team captures several large features that cannot fit into a single sprint. What should the Product Owner do next according to SBOK?

1. Move the epics directly into the Sprint Backlog and start tasking.
2. Split the epics into user stories and commit them to the next sprint immediately.
3. Record the epics in the Prioritized Product Backlog and use them as input to release planning; decompose into user stories when closer to implementation.
4. Convert the epics into detailed technical specifications for developers.

Correct Answer: C — Record the epics in the Prioritized Product Backlog and use them as input to release planning; decompose into user stories when closer to implementation.

Explanation: In SBOK, epics are created early, prioritized for release planning, and only later split into user stories for estimation and sprint commitment. Pulling epics straight into a sprint or writing full specifications is not appropriate.