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?

  1. Start planning the next sprint and update the team velocity.
  2. Ship the accepted deliverables to business stakeholders and obtain the Working Deliverables Agreement.
  3. Conduct only the sprint retrospective to capture lessons learned.
  4. 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.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Become an AI-First Agile Leader!

HK School of Management and Technology helps you apply AI to Agile work with practical, prompt-based workflows for real-world Scrum challenges. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More