The Developers
PSM I PSM I · Scrum Team & Accountabilities
Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. The word Developers is deliberately broad: it covers everyone who does the work of creating the Increment, whatever their specialty — programmers, testers, designers, analysts, and anyone else whose work contributes. The specific skills needed are often broad and vary with the domain of work, and the Guide deliberately gives no titles or sub-roles within the Developers. There is no hierarchy among them, and no separate testing team or design team inside the Scrum Team. A tester is a Developer. A designer is a Developer. This matters for the exam because questions often try to reintroduce traditional job titles and reporting lines into the Scrum Team — the Guide's answer is always that the Developers are one group, collectively accountable for the work.
The Developers are always accountable for four things: creating a plan for the Sprint — the Sprint Backlog; instilling quality by adhering to the Definition of Done; adapting their plan each day toward the Sprint Goal; and holding each other accountable as professionals. Each of these is worth understanding precisely. Creating the Sprint Backlog means the Developers decide how much work to take on and how to do it; nobody else writes their plan. Instilling quality by adhering to the Definition of Done means quality is not inspected in afterwards by someone else — the Developers build it in by following the agreed standard. Adapting the plan each day means the Sprint Backlog is a living plan, updated as the Developers learn more, with the Daily Scrum as the main moment for that adaptation. And holding each other accountable as professionals means the Developers manage their own standards of work — they do not wait for the Scrum Master or a manager to enforce quality or effort.
Two accountabilities deserve special attention because the exam tests them repeatedly. First, sizing: the Developers who will do the work are responsible for sizing Product Backlog items. The Product Owner may influence the Developers by helping them understand the work and select trade-offs, but the estimate itself belongs to the people doing the work. Any exam option where the Product Owner or Scrum Master estimates the work is wrong. Second, the Sprint Backlog: it is a plan by and for the Developers. Only the Developers change it. The Product Owner cannot add items to it mid-Sprint unilaterally, and the Scrum Master cannot rewrite it. If scope needs to change, the Developers and the Product Owner negotiate — and the Developers update their own plan.
Developers and the events
The Developers participate in every event, and one event belongs to them specifically: the Daily Scrum is a 15-minute event for the Developers, who use it to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The Product Owner and Scrum Master participate only if they are actively working on items in the Sprint Backlog, and then they participate as Developers. In Sprint Planning, the Developers are central to all three topics: they help shape the Sprint Goal, they decide what can be Done in the Sprint, and they create the plan for how the chosen work gets done. At the Sprint Review, the Developers are part of the Scrum Team presenting results to stakeholders. At the Sprint Retrospective, the Developers inspect how the Sprint went alongside the rest of the team. The exam often tests event participation — who must attend, who may attend, and who owns each event — so knowing that the Daily Scrum is the Developers' event is essential.
Worked scenario
A Product Owner is frustrated that the Developers' estimates seem too high and asks the Scrum Master to challenge them to commit to more work in the Sprint. The Scrum Master refuses to pressure the team, and the Product Owner complains that the Developers are not being team players. What does the Guide say? Sizing is the Developers' responsibility, and the Product Owner may influence them by helping them understand the work and the trade-offs — not by overriding the estimates or using the Scrum Master as leverage. The Developers decide what can be Done in a Sprint, based on their past performance, their capacity, and their Definition of Done. Pressuring a team to take on more than it can complete does not create more value; it creates unfinished work, broken transparency, and a Sprint Goal at risk. The right conversation is about trade-offs: if the Product Owner wants more done, the discussion is about smaller items, clearer requirements, or removing impediments — not about inflating commitments.
Developers and quality
Quality in Scrum is built in, not inspected in afterwards. The Developers instill quality by adhering to the Definition of Done — which means the standard is applied to every item, every Sprint, without exception. There is no separate quality phase, no handoff to a testing department, and no Product Owner acceptance gate that substitutes for the Definition of Done. When the Developers discover that an item cannot meet the standard within the Sprint, the honest response is to say so, renegotiate scope with the Product Owner, and carry the unfinished work back to the Product Backlog — not to quietly lower the standard. This honesty is what makes the Increment trustworthy: stakeholders know that what is presented at the Sprint Review genuinely meets the agreed standard, because the Developers enforced it themselves.
Developers and the Product Owner
The relationship between the Developers and the Product Owner is a partnership with a clear boundary. The Product Owner decides what is most valuable and in what order; the Developers decide how much they can do and how to do it. The two sides meet constantly — in refinement, in Sprint Planning, in the Daily Scrum when the Product Owner has questions to answer, and whenever scope needs renegotiating mid-Sprint. The partnership works when each side respects the other's accountability: the Product Owner does not tell the Developers how to build, and the Developers do not tell the Product Owner what is valuable. When the boundary blurs — the Product Owner dictating technical approaches, or the Developers refusing to build what the Product Owner ordered — the Scrum Master coaches both sides back to their accountabilities. The exam tests this boundary through scenarios where one side oversteps, and the correct answer is always the one that restores the boundary.
Exam traps to watch for
- Treating testers, designers, or analysts as separate from Developers. Everyone who creates the Increment is a Developer; there are no sub-teams or titles.
- Letting the Product Owner or Scrum Master estimate work. The Developers who will do the work are responsible for sizing.
- Letting anyone but the Developers change the Sprint Backlog. It is a plan by and for the Developers; scope changes are negotiated with the Product Owner.
- Thinking the Daily Scrum is a status meeting for the Product Owner or Scrum Master. It is the Developers' event, for inspecting progress toward the Sprint Goal.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.Who are the Developers in a Scrum Team?
Explanation: Developers are the people in the Scrum Team committed to creating any aspect of a usable Increment each Sprint — whatever their specialty, including testers, designers, and analysts. Limiting the term to coders is wrong. People outside the Scrum Team are not Developers even if they work on the product. The Scrum Master and Product Owner are separate accountabilities; they participate as Developers only when actively working on Sprint Backlog items, but that does not define the Developers.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Scrum Team
Q2.Who is responsible for sizing Product Backlog items?
Explanation: The Developers who will do the work are responsible for the sizing. The Product Owner may influence the Developers by helping them understand and select trade-offs, but does not size the work. The Scrum Master facilitates but does not estimate. There is no external estimation role in Scrum.
Exam objective: PSM I Focus Area: Managing Products with Agility — Product Backlog Management
Q3.Which of the following are the Developers ALWAYS accountable for?
Explanation: The Developers are always accountable for creating a plan for the Sprint (the Sprint Backlog), instilling quality by adhering to a Definition of Done, adapting their plan each day toward the Sprint Goal, and holding each other accountable as professionals. Ordering the backlog and defining the Product Goal belong to the Product Owner. The Sprint Review is presented by the whole Scrum Team, not the Developers alone. Removing impediments and coaching the organization are Scrum Master services.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Scrum Team
Q4.During a Sprint, the Product Owner wants to add a new item to the Sprint Backlog. What is the correct approach?
Explanation: The Sprint Backlog is a plan by and for the Developers. Scope may be clarified and renegotiated with the Product Owner as more is learned, but the Developers update their own plan. The Product Owner cannot add items unilaterally. The Scrum Master does not change the Sprint Backlog. And the claim that it cannot change at all is wrong — it is updated throughout the Sprint as more is learned.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q5.Which statement about the Daily Scrum is TRUE?
Explanation: The Daily Scrum is a 15-minute event for the Developers, used to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not run by the Scrum Master to assign tasks — the Developers run it themselves. It is not a status report to the Product Owner. And it is not optional; it is one of the five events, held every working day of the Sprint.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q6.A tester and a UX designer are part of a Scrum Team. How does the Scrum Guide classify them?
Explanation: Everyone committed to creating any aspect of a usable Increment is a Developer, including testers and designers. They are not stakeholders — they are inside the Scrum Team. There are no sub-teams within a Scrum Team. And there is no part-time or limited membership category in the Guide.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Scrum Team
Q7.The Product Owner thinks the Developers' estimates are too high and asks the Scrum Master to push the team to commit to more work. What does the Scrum Guide support?
Explanation: The Developers who will do the work are responsible for sizing; the Product Owner may influence them by helping them understand and select trade-offs. Pressuring the team to overcommit creates unfinished work and broken transparency. The Product Owner cannot override estimates or set Sprint scope directly — the Developers decide what can be Done in the Sprint. Estimates belong to the Developers, not the Product Owner.
Exam objective: PSM I Focus Area: Managing Products with Agility — Product Backlog Management
Q8.How do Developers instill quality into their work, according to the Scrum Guide?
Explanation: Developers instill quality by adhering to a Definition of Done. The Scrum Master does not review the Developers' work. The Product Owner does not test everything — the Increment is inspected at the Sprint Review, and work counts when it meets the Definition of Done. Writing more code is not quality; meeting the agreed quality standard is.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Done
Q9.Which statement about Developers is FALSE?
Explanation: There are no hierarchies within a Scrum Team, and no titles among Developers — the idea of senior Developers directing juniors contradicts the Guide. The other three statements are all true: Developers adapt their plan each day toward the Sprint Goal, hold each other accountable as professionals, and create the Sprint Backlog.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Scrum Team