SkarpChapter 6 of 21
Scrum Accountabilities III: Developers and Creating the Increment
Zoom in on Developers as the people who turn ideas into value each Sprint, and clarify how their accountability differs from the older ‘Development Team’ concept.
From Development Team to Developers: The 2020 Shift
Why This Module Matters
We focus on the people who turn Product Backlog items into a usable Increment: Developers. Understanding their accountability is heavily tested on PSM I.
The 2020 Terminology Shift
Before late 2020, Scrum used the term Development Team as a sub‑team. Since the November 2020 Scrum Guide, this concept was removed in favor of a single Scrum Team.
Canonical Definition
Memorize this for the exam: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."
One Scrum Team
There is now one Scrum Team with three accountabilities: Product Owner, Scrum Master, and Developers. No sub‑teams, no separate Development Team goal.
Exam Relevance
On PSM I, any option using "Development Team" is legacy wording. Modern, correct wording is Developers, unless the question explicitly talks about history.
Who Are Developers? Scope, Skills, and Cross‑Functionality
Developers Are More Than Coders
In Scrum, Developers include programmers, testers, UX designers, writers, DevOps, data scientists—anyone who helps create the Increment.
Canonical Definition Reminder
Memorize: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."
Cross‑Functional Group
As a group, Developers must have all skills needed to create a usable Increment: design, build, test, integrate, document, operate, and more.
No Internal Titles
Scrum ignores internal titles like "QA lead" or "senior dev". For Scrum purposes, everyone doing the work is simply a Developer.
No Sub‑Teams
Inside the Scrum Team there are no sub‑teams like "frontend" vs "backend". All Developers are jointly accountable for the Increment.
Exam Signal
If a question treats only coders as Developers and others as outsiders, that conflicts with Scrum. Anyone creating any aspect of the Increment is a Developer.
Developers and the Increment: Quality, DoD, and Value
What Is an Increment?
An Increment is "a concrete stepping stone toward the Product Goal." It is a real, usable addition to the product.
Definition of Done
The Definition of Done is "a formal description of the state of the Increment when it meets the quality measures required for the product."
Developers Own Quality
Developers are accountable for ensuring all work meets the Definition of Done. If it does not, it is not part of the Increment.
Usable and Potentially Releasable
Each Increment must be in a state that could be released. Unintegrated or untested code is not a done Increment.
Multiple Increments
Developers may create multiple Increments in a Sprint. All must meet the Definition of Done; the sum is inspected at Sprint Review.
Exam Tip
If a question asks who is responsible for the quality of the Increment or applying the Definition of Done, the answer is Developers.
Sprint Backlog Ownership: Developers Plan the Work
Sprint Backlog Definition
The Sprint Backlog is "the Sprint Goal (why), the set of Product Backlog items selected (what), and an actionable plan for delivering the Increment (how)."
Developers Own the Sprint Backlog
Developers decide how many Product Backlog items to pull into the Sprint, based on capacity and past performance.
Creating the Plan
Developers create the actionable plan: technical approach, task breakdown, and sequencing needed to deliver the Increment.
Updating the Plan
Only Developers update the Sprint Backlog as they learn. It is a living plan that evolves throughout the Sprint.
Sprint Goal as Anchor
Developers commit to achieving the Sprint Goal, not to a frozen task list. They may adjust the how while keeping the goal achievable.
Exam Trap Alert
Any answer saying the Scrum Master or Product Owner owns the Sprint Backlog is wrong. It is for and by Developers.
Self‑Management: How Developers Decide Who Does What, When, and How
Self‑Managing Developers
The Scrum Team is self‑managing. Developers decide how best to accomplish the work, without external task assignment or micro‑management.
No External Task Assignment
Product Owners, Scrum Masters, and line managers do not assign tasks. Developers collectively decide who does what.
Who Does What, When, How
Developers choose how to share work, which practices and tools to use, and how to sequence tasks to meet the Sprint Goal.
Daily Scrum for Self‑Management
The Daily Scrum is for Developers to inspect progress and adapt their plan. It is not a status meeting for reporting to a manager.
Accountability Remains
Self‑management is not chaos. Developers are still accountable for quality and progress toward the Sprint Goal.
Exam Signal
Any option where the Scrum Master or Product Owner assigns tasks conflicts with Scrum’s self‑management principle.
Case Study: A Day in the Life of Developers Creating the Increment
Sprint Planning in Practice
PO shares top Product Backlog items. The team sets a Sprint Goal: "Reduce checkout abandonment via guest checkout." Developers select items and create tasks.
Daily Work and Swarming
At the Daily Scrum, Developers see the database migration is risky. Three swarm on it while others handle UX and tests to protect the Sprint Goal.
Adapting the Sprint Backlog
When an integration issue appears, Developers update the Sprint Backlog: add tasks, drop a low‑value cosmetic change, keep the Sprint Goal achievable.
Applying the Definition of Done
Before merging, Developers ensure criteria, tests, security checks, and docs meet the Definition of Done, creating a truly usable Increment.
Review and Release
At the Sprint Review, the Increment is inspected with stakeholders. The Product Owner decides to release it based on observed value.
Continuous Improvement
In the Retrospective, Developers refine their migration checklist, improving how they will create future Increments.
Developers vs Product Owner vs Scrum Master: Clear Boundaries
Three Canonical Definitions
PO: "accountable for maximizing the value of the product". SM: "accountable for establishing Scrum". Developers: "committed to creating any aspect of a usable Increment."
Product Owner Focus
The Product Owner owns the Product Backlog, decides what to build and why, and steers toward the Product Goal and Sprint Goals.
Developers Focus
Developers own the Sprint Backlog and the plan. They decide how to build, who does what, and ensure the Increment meets the Definition of Done.
Scrum Master Focus
The Scrum Master coaches on Scrum, facilitates, and removes impediments. They do not manage or command Developers.
Accountability Boundaries
Increment quality: Developers. Product value: Product Owner. Scrum implementation: Scrum Master. Do not mix these up on the exam.
Typical Exam Trap
Statements like "PO assigns tasks" or "SM is responsible for the Increment" are wrong. Developers are accountable for the Increment.
Thought Exercise: Spot the 2017 vs 2020 Terminology
Use this quick exercise to train your eye for outdated vs current Scrum wording.
For each statement, decide:
- Is it aligned with the 2020+ Scrum Guide?
- If not, how would you rephrase it using current terminology?
- "The Development Team is responsible for delivering the Increment."
- "The Development Team reports its progress to the Scrum Master in the Daily Scrum."
- "Developers collaborate with the Product Owner to understand Product Backlog items before selecting them for the Sprint."
- "The Development Team and Product Owner have separate Sprint Goals."
- "Developers own the Sprint Backlog and adapt it throughout the Sprint."
Pause and answer before reading the guidance below.
Suggested answers and reasoning
- Outdated term. Rephrase: "Developers are responsible for creating the Increment." Note: "responsible" in everyday language is fine, but "accountable" is the keyword Scrum uses for roles.
- Wrong both in terminology and behavior. Rephrase: "Developers use the Daily Scrum to inspect progress toward the Sprint Goal and adapt their plan. They do not report status to the Scrum Master."
- Correct and current. It uses "Developers" and describes proper collaboration.
- Incorrect. There is one Sprint Goal for the whole Scrum Team. Rephrase: "The Scrum Team has a single Sprint Goal that aligns the work of Developers and the Product Owner."
- Correct and current. It matches the 2020+ Guide: Developers own and adapt the Sprint Backlog.
Quick Check: Developers and the Sprint Backlog
Test your understanding of who owns what in Scrum.
During a Sprint, a stakeholder asks the Scrum Master to add a new high‑priority item into the Sprint Backlog. According to Scrum, who has the authority to change the Sprint Backlog?
- The Scrum Master, because they facilitate the Scrum events
- The Product Owner, because they own the Product Backlog and priorities
- The Developers, because they own the Sprint Backlog and the plan for delivering the Increment
- Any stakeholder, as long as the Product Owner agrees
Show Answer
Answer: C) The Developers, because they own the Sprint Backlog and the plan for delivering the Increment
The Sprint Backlog is for and by Developers: they own it and adapt it during the Sprint. The Product Owner owns the Product Backlog and may negotiate scope, but cannot directly change the Sprint Backlog. The Scrum Master facilitates but does not own any backlog.
Quick Check: Increment and Definition of Done
Another short quiz to reinforce key concepts.
At the end of the Sprint, some work items are coded but not tested according to the Definition of Done. What should Developers do?
- Include the items in the Increment and test them next Sprint
- Exclude the items from the Increment because they do not meet the Definition of Done
- Ask the Product Owner to approve a temporary exception to the Definition of Done
- Mark the items as done because the coding work is complete
Show Answer
Answer: B) Exclude the items from the Increment because they do not meet the Definition of Done
If work does not meet the Definition of Done, it is not part of the Increment. Developers must not present or count it as done. It returns to the Product Backlog for future consideration.
Key Term Flashcards: Developers and the Increment
Use these flashcards to lock in key definitions and role boundaries. Say the answer out loud, then flip to check.
- Canonical definition of Developers
- Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
- Who owns the Sprint Backlog?
- Developers own the Sprint Backlog, including the selected Product Backlog items and the actionable plan for delivering the Increment.
- What is an Increment?
- An Increment is a concrete stepping stone toward the Product Goal.
- What is the Definition of Done?
- The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
- Who is accountable for the quality of the Increment?
- Developers are accountable for ensuring the Increment meets the Definition of Done and is usable.
- Who decides what to build and in which order?
- The Product Owner, who is accountable for maximizing the value of the product and owns the Product Backlog.
- Who is accountable for establishing Scrum as defined in the Scrum Guide?
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
- Which term is deprecated after the 2020 Scrum Guide?
- The term "Development Team" is deprecated; the correct term is "Developers" within a single Scrum Team.
- What three elements compose the Sprint Backlog?
- The Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how).
- What is the Sprint Goal?
- The Sprint Goal is the single objective for the Sprint.
Bringing It Together and Next Steps in Your Study Path
Core Memory: Developers
Use Developers, not "Development Team". Developers are anyone committed to creating any aspect of a usable Increment each Sprint.
Increment and Quality
Developers are accountable for the Increment and for applying the Definition of Done. Undone work is not part of the Increment.
Owning the Sprint Backlog
Developers own and adapt the Sprint Backlog and decide who does what, when, and how. No one assigns tasks to them.
Clear Role Boundaries
PO: value and Product Backlog. Developers: execution and Increment quality. SM: Scrum and coaching. Keep these separations clear for the exam.
Skarp Study Next Steps
Use the diagnostic, mock exam, and spaced review queue to pressure‑test your understanding of Developer accountabilities.
Looking Ahead
Next modules will link Developer accountabilities to events like Sprint Planning and Daily Scrum so you can decode exam scenarios quickly.
Key Terms
- Scrum
- Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
- Sprint
- Sprints are the heartbeat of Scrum, where ideas are turned into value.
- Increment
- An Increment is a concrete stepping stone toward the Product Goal.
- Developers
- Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
- Scrum Team
- The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
- empiricism
- Scrum is founded on empiricism and lean thinking.
- Sprint Goal
- The Sprint Goal is the single objective for the Sprint.
- Product Goal
- The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
- Scrum Master
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
- Product Owner
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
- Sprint Backlog
- The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
- Product Backlog
- The Product Backlog is an emergent, ordered list of what is needed to improve the product.
- Definition of Done
- The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.