Ship Deliverables
This process transfers accepted deliverables to the appropriate business stakeholders and completes their move into operational use. A formal Working Deliverables Agreement serves as evidence that the sprint has been successfully closed.
Key Points
- Happens after deliverables have been accepted against agreed acceptance criteria.
- Focuses on handing off to business stakeholders, including any release, training, and documentation needed for use.
- The Working Deliverables Agreement formally confirms successful sprint completion and stakeholder receipt.
- Establishes ownership and support arrangements for the shipped items going forward.
Example
After a sprint, the team finishes and gets acceptance for a new reporting dashboard. The project manager coordinates deployment to the client environment, provides the user guide and brief training, and obtains a signed Working Deliverables Agreement from the product owner and operations lead to confirm the sprint is complete.
PMP Example Question
At the end of a sprint, all user stories are accepted. What should the project manager do next to formally close delivery for the sprint?
- Start planning the next sprint and update the team velocity.
- Ship the accepted deliverables to business stakeholders and obtain the Working Deliverables Agreement.
- Conduct only the sprint retrospective to capture lessons learned.
- Re-estimate the product backlog for future releases.
Correct Answer: B — Ship the accepted deliverables and document completion with the Working Deliverables Agreement
Explanation: Shipping accepted deliverables and securing the formal agreement confirms stakeholder receipt and marks the sprint as successfully completed.
HKSM