CSM Exam Results

The described scenario aligns with"Individuals and Interactions over Processes and Tools", one of the four core Agile Values from the Agile Manifesto. This value emphasizes the importance of collaboration, communication, and teamwork over reliance on rigid processes or tools. Scrum encourages team members to work together closely to solve problems and deliver high-quality software.

Why the other options are incorrect:

A. Individuals and Interactions over Working Software:While this value mentions "Working Software," the scenario focuses on collaboration among team members, which relates more to prioritizing individuals and interactions.

C. Individuals and Interactions over Contract Negotiation:This value applies to collaboration with stakeholders and customers rather than collaboration within the team.

D. Individuals and Interactions over Customer Collaboration:While customer collaboration is essential, the scenario specifically highlights collaboration among team members.

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.

Adone Incrementisusable, meaning it meets the Scrum Team's Definition of Done and can be used or inspected by stakeholders. While the Increment may not always be released to end users, it must be in a usable state to ensure transparency and enable feedback.

According to the2020 Scrum Guide:

An Increment is a concrete step toward the Product Goal.

Each Increment must meet the Definition of Done, ensuring it is usable and provides value, regardless of whether it is immediately released.

Why the other options are incorrect:

A. Prescriptive:Scrum is not prescriptive about how work is done, and "prescriptive" is not a characteristic of a done Increment.

B. Estimable:"Estimable" applies to Product Backlog items but is not a characteristic of a done Increment.

D. Released:While an Increment may be released, it is not a required characteristic. It simply must be in a usable state.

Product Backlog management is primarily the responsibility of theProduct Owner. One of their key activities is toclearly express Product Backlog items, ensuring they are transparent and understandable for the Developers. This helps the Scrum Team deliver valuable Increments.

According to the2020 Scrum Guide, Product Backlog management includes:

Clearly expressing Product Backlog items.

Ordering the items to maximize value.

Ensuring the Product Backlog is transparent, visible, and understood.

Why the other options are incorrect:

B. Creating Sprint tasks:Sprint tasks are part of the Developers’ detailed planning during the Sprint and are not part of Product Backlog management.

C. Facilitating the Daily Scrum:This is a responsibility of the Developers, and the Scrum Master may only facilitate if explicitly requested.

D. Planning the Sprint Backlog:The Sprint Backlog is planned during Sprint Planning and is primarily the Developers' responsibility, not part of Product Backlog management.