Create Deliverables

Create Deliverables is the process in which the Scrum Team executes the work selected in the Sprint Backlog to produce the sprint's deliverables (the increment).

Key Points

  • Happens during the sprint as the team builds the planned increment.
  • Guided by the Sprint Backlog and refined through ongoing collaboration.
  • Outputs are the Sprint Deliverables that meet the Definition of Done.
  • Progress is inspected and adapted through daily coordination and feedback.

Example

During a two-week sprint, the Scrum Team picks user stories from the Sprint Backlog, designs and codes features, writes tests, and updates documentation. By the end of the sprint, they produce a tested, integrated increment that meets the Definition of Done and is ready for review.

PMP Example Question

During a sprint, the team is developing, testing, and integrating backlog items to produce a potentially shippable increment. Which process does this describe?

  1. Sprint Planning
  2. Control Quality
  3. Create Deliverables
  4. Sprint Review

Correct Answer: C — Create Deliverables

Explanation: Create Deliverables is the execution work of building the sprint's deliverables from the Sprint Backlog, resulting in the increment that meets the Definition of Done.

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


Run the drill before the incident runs you

Design, run and prove OT drills and tabletop exercises before an incident tests your team. OT Incident Drills and Exercises includes 24 lessons and practical exercise materials, delivered through HKSM Courses for US$47 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course