HKSM

Product Releases are packaged increments of accepted work prepared for deployment, including release notes, versioning, and supporting materials. In SBOK, they are the output of Ship Deliverables and become inputs for operations, support, and project/sprint retrospectives.

Key Points

• Output of the Ship Deliverables process and input to operations, support, and retrospectives.
• Bundles accepted deliverables with release notes, deployment steps, and readiness confirmations.
• Aligned to the release plan and minimum marketable features or similar slices of value.
• Validated against Definition of Done, nonfunctional requirements, and compliance needs.
• Versioned and traceable to user stories, epics, and acceptance criteria.
• Communicated to stakeholders to set expectations about scope, timing, and known issues.

Purpose

Product Releases make completed increments consumable by end users and operations. They provide a clear, agreed package of scope, quality, and instructions so value can be deployed safely and predictably.

They also serve as a baseline for support, reporting, benefits tracking, and lessons learned in sprint or project retrospectives.

Key Terms & Clauses

• Release Plan: roadmap that groups product backlog items into target releases or windows.
• Minimum Marketable Feature (MMF): smallest set of functionality that delivers user-visible value.
• Definition of Done (DoD): quality bar that each item in the release must meet.
• Release Notes: summary of features, fixes, known issues, and any required actions.
• Go/No-Go Criteria: readiness checks such as tests passed, approvals obtained, and rollback prepared.
• Versioning and Tagging: identifiers that link code, configuration, and documentation to the release.
• Rollback Plan: steps to revert if the deployment causes unacceptable impact.

How to Develop/Evaluate

1. Collect Inputs: gather accepted deliverables from Demonstrate and Validate Sprint and confirm DoD.
2. Assemble Scope: select items per the release plan or MMF boundaries and check dependencies.
3. Verify Readiness: complete regression, performance, security, and compliance checks.
4. Create Artifacts: draft release notes, deployment and rollback steps, and training or FAQs.
5. Version and Package: tag code, generate build artifacts, and prepare infrastructure changes.
6. Go/No-Go Review: Product Owner, Scrum Master, team, and key stakeholders confirm readiness.
7. Evaluate Quality: review defect trends, deployment test results, and risk status before shipping.

How to Use

Use Product Releases to coordinate deployment with operations, communicate scope to stakeholders, and enable user adoption through clear notes and training.

Feed outcomes back into retrospectives to improve release planning, automation, and risk controls. Update the prioritized product backlog with any deferred items, follow-up work, or discovered defects after release.

Example Snippet

• Release ID: 2025.03.0.
• Scope: 8 user stories from Sprint 6, including 2 MMFs.
• Quality Status: all acceptance tests passed; regression suite 100 percent; performance within SLOs.
• Deployment Steps: apply DB migration v3.2, deploy service v1.8, enable feature flag "NewUI".
• Rollback: revert to tag 2025.02.2 and restore snapshot S6-RC1.
• Known Issues: minor UI glitch on legacy browser; workaround documented.

Risks & Tips

• Risk: hidden dependencies cause failed deployments. Tip: maintain a release checklist and dependency map.
• Risk: insufficient regression leads to escaped defects. Tip: automate tests and require green pipelines.
• Risk: environment drift between test and prod. Tip: use infrastructure as code and consistent configurations.
• Risk: unclear scope confuses stakeholders. Tip: publish concise release notes and change summaries.
• Risk: big-bang releases increase impact. Tip: use small batches, feature toggles, and canary or phased rollouts.
• Risk: missing approvals delay go-live. Tip: define go/no-go criteria and obtain sign-offs early.

PMP/SCRUM Example Question

During Ship Deliverables, the team bundles accepted work with release notes, deployment instructions, and a rollback plan to hand over to operations. What output is being produced?

1. Product Increment
2. Accepted Deliverables
3. Product Releases
4. Prioritized Product Backlog

Correct Answer: C — Product Releases

Explanation: Product Releases are the packaged, deployable output of Ship Deliverables that include notes and instructions. The increment and accepted deliverables exist earlier; the prioritized product backlog is a planning artifact.