Question 54 - PSPO-I discussion

The Developers are the people in the Scrum Team who are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done is used to assess when work is complete on the product Increment.

The amount of work required of the Developers to complete a Product Backlog item selected during the Sprint Planning depends on the Definition of Done. The Definition of Done may vary from one Scrum Team to another, depending on the context and domain of work. However, it must be consistent within one team. If there are multiple Scrum Teams working on one product, they must share a common Definition of Done. If there is an organizational standard for a Definition of Done, all Scrum Teams must follow it as a minimum.

The Developers must ensure that each Product Backlog item they complete during a Sprint meets the Definition of Done. This means that they must perform all the necessary tasks and activities to deliver a high-quality product functionality that is usable, valuable, and potentially releasable. This may include analysis, design, development, testing, documentation, integration, deployment, or any other aspects that contribute to the quality and usability of the product.

The other options are not valid or relevant measures for the amount of work required of the Developers to complete a Product Backlog item. They are either too vague, arbitrary, or unrealistic. They are:

As much as they can fit into the Sprint, with remaining work deferred to the next Sprint: This is a too vague and unrealistic measure for the amount of work required of the Developers. It does not account for the quality or value of the product functionality delivered. It also does not respect the timebox or scope of the Sprint. It may lead to incomplete or unfinished work, technical debt, or scope creep.

All development work and at least some testing: This is a too arbitrary and insufficient measure for the amount of work required of the Developers. It does not account for the quality or value of the product functionality delivered. It also does not respect the Definition of Done or the potentially releasable nature of the Increment. It may lead to low-quality or unusable work, defects, or rework.

A proportional amount of time on analysis, design, development, and testing: This is a too restrictive and prescriptive measure for the amount of work required of the Developers. It does not account for the complexity or variability of the product functionality delivered. It also does not respect the self-organization or cross-functionality of the Developers. It may lead to over-engineering or waste.

Scrum Guide: https://www.scrumguides.org/scrum-guide.html

Definition of Done: https://www.scrum.org/resources/what-is-a-definition-of-done

Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum