HKSM
Potentially Shippable Deliverables from Projects
Project teams produce increments that could be released, and these artifacts are used to align work at the program and portfolio levels. Each Sprint ends with a finished product increment or deliverable. The user stories in that increment meet the team's Definition of Done as well as their specific acceptance criteria.
Key Points
- Serve as inputs for coordination and decision making across programs and portfolios.
- Completed at the end of each Sprint as a usable product increment or deliverable.
- Considered potentially releasable only when both the Definition of Done and acceptance criteria are satisfied.
- Enable integration, demos, feedback, and release planning across multiple projects.
Example
A program manages three agile teams building a healthcare portal. After a Sprint, Team A delivers a secure login feature that passes all tests, meets the Definition of Done, and satisfies its acceptance criteria. The program manager uses this increment to plan the next integration, coordinate dependencies with Teams B and C, and update portfolio release timelines.
PMP Example Question
Which statement best describes potentially shippable deliverables from projects in an agile environment?
- Draft features used only for internal testing between Sprints.
- Completed increments at the end of a Sprint that meet the Definition of Done and acceptance criteria and support program/portfolio coordination.
- Any backlog items committed during Sprint Planning, regardless of completion status.
- Only items that have been released to end users during a production deployment.
Correct Answer: B — Completed increments meeting DoD and acceptance criteria used for higher-level coordination
Explanation: Potentially shippable deliverables are finished, test-passed increments produced at Sprint end that satisfy the Definition of Done and acceptance criteria and are used to align work at program and portfolio levels.
