CSM Exam Dumps - Certified ScrumMaster Exam

TheSprint Backlogis owned solely by theDevelopers, as they are responsible for planning, managing, and executing the work required to meet the Sprint Goal. The Sprint Backlog is ahighly visible, real-time planfor delivering the Increment. It includes:

TheSprint Goal.

The set of Product Backlog items selected for the Sprint.

A plan for delivering the Increment.

According to the2020 Scrum Guide, the Developers:

Have full ownership and accountability over the Sprint Backlog.

Decide how to adapt their work plan daily to achieve the Sprint Goal.

Why the other options are incorrect:

A. Scrum Master:The Scrum Master facilitates the Scrum process but does not own the Sprint Backlog.

C. Product Owner:The Product Owner manages the Product Backlog, not the Sprint Backlog.

D. Scrum Team:While the Sprint Goal is owned by the entire Scrum Team, the Sprint Backlog is specifically managed and executed by the Developers.

Across-functional Scrum Teamis one that has all the skills necessary to deliver ausable Incrementof the product. This ensures that the team is not dependent on external groups to complete their work, enabling them to deliver value independently.

According to the2020 Scrum Guide:

Scrum Teams are cross-functional and self-managing.

Cross-functionality means the team includes all the necessary skills (e.g., development, testing, design) to complete the work in a Sprint and deliver an Increment.

Why the other options are incorrect:

A. Divided into sub-teams:Scrum discourages dividing teams based on function. The team should be collaborative and cross-functional.

B. Distributed:While Scrum Teams can be distributed geographically, this term does not define their ability to deliver a usable Increment.

D. Difficult to manage:A cross-functional Scrum Team is self-managing and does not require external management.

Fromself-organizing teams,the best architecture, requirements, and designsemerge. This aligns with one of theAgile Manifesto Principles, which states:

"The best architectures, requirements, and designs emerge from self-organizing teams."

Self-organizing teams have the autonomy to make decisions, collaborate effectively, and adapt their processes to deliver high-quality solutions.

Self-organizing teams work without being micromanaged, leveraging their expertise and collective intelligence to solve complex problems and create innovative solutions.

Why the other options are incorrect:

A. The best process flows, user stories and requirements:While self-organizing teams improve processes, the Agile principle specifically mentions architecture, requirements, and designs.

C. The best designs, user stories and Sprint Backlog:The Sprint Backlog is an artifact, not an outcome of self-organization.

D. The best architecture, user stories and requirements:User stories are part of backlog items, but the principle focuses on architecture, requirements, and designs.

Scrum teams plan workone Sprint at a time, using theSprint Planning eventto adapt the Sprint Backlog based on what was learned in previous Sprints. This approach aligns with Scrum'sempirical process control, which relies on inspection and adaptation to plan effectively.

According to the2020 Scrum Guide:

Sprint Planning creates aSprint Backlog, which includes the Sprint Goal, selected Product Backlog items, and the plan to deliver them.

Teams adjust their plans Sprint by Sprint, responding to new information, feedback, and changing circumstances.

Why the other options are incorrect:

A. One release at a time, adjusting the number of Sprints to the prior releases’ average velocity:Scrum does not prescribe release-driven planning or adjusting Sprint duration based on velocity.

C. One project at a time, adjusting each Sprint Backlog Item to meet the release date negotiated at inception:Scrum encourages iterative planning within Sprints, not fixed plans tied to predetermined release dates.

D. One Sprint at a time in the Product Backlog Refinement meeting with participation of stakeholders:Product Backlog Refinement is an ongoing activity, not a Sprint planning process. Stakeholders typically participate in Sprint Reviews, not in backlog refinement.

The correct statement is:An Increment must be in a usable condition and meet the Definition of Done. Each Increment builds upon previous Increments and must be complete, usable, and meet the agreed-uponDefinition of Doneso it can be inspected during the Sprint Review. Whether or not the Increment is released is a separate decision made by the Product Owner.

According to the2020 Scrum Guide:

An Increment is the result of work done during a Sprint and must meet the Definition of Done.

The Increment isusable, even if the Product Owner decides not to release it.

Why the other options are incorrect:

A. It must have all of the requirements that need to be in the product before the Product Owner will release it:Increments do not require all requirements to be complete before being usable or inspectable. Scrum is iterative, delivering value incrementally.

B. Is not releasable until the Product Owner determines it is done:The Product Owner does not determine whether the Increment is "done"; the team’s adherence to the Definitionof Done determines this.

D. Is not releasable until it has all of the features to be a Minimally Viable Product:Each Increment must meet the Definition of Done, regardless of whether it meets all features for an MVP.