Working Deliverables Agreement

A policy that a deliverable is officially accepted only after it meets its defined acceptance criteria and the customer or sponsor provides formal business approval and signs off.

Key Points

  • Acceptance criteria are defined and testable before work is performed.
  • Formal approval authority rests with the customer or sponsor, not the project team.
  • Sign-off is documented and indicates the deliverable is ready for release or integration.
  • In agile, this happens repeatedly at reviews or demos for each increment or iteration.

Example

During a sprint review for a new login feature, the product owner verifies that all acceptance criteria are met (multi-factor prompt, error handling, lockout after failed attempts). The sponsor provides formal sign-off in the tracking tool, marking the feature as accepted and ready for deployment.

PMP Example Question

Which statement best describes a Working Deliverables Agreement in an agile project?

  1. It outlines how scope changes are escalated to the change control board.
  2. It requires that deliverables meeting acceptance criteria receive formal approval and sign-off from the customer or sponsor.
  3. It defines how the team prioritizes the product backlog each iteration.
  4. It specifies the tools used for defect tracking and reporting.

Correct Answer: B — Deliverables meeting acceptance criteria receive formal approval and sign-off.

Explanation: The agreement emphasizes that only deliverables that satisfy predefined acceptance criteria are formally accepted by the customer or sponsor.

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.

Seven 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 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