When multiple Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint?
(choose the best answer)
Correct Answer:
A
When multiple Scrum Teams are working on the same product, they should integrate their Increments every Sprint because:
✑ It allows them to accurately inspect what is done and what is potentially releasable. By integrating their work frequently, they can ensure that the product is in a usable and valuable state at the end of each Sprint, and that it meets the Definition of Done and the Sprint Goal.
✑ It enables them to adapt to changes and feedback faster. By integrating their work frequently, they can reduce the complexity and risk of integration, and discover and resolve any issues or dependencies sooner. They can also incorporate any new insights or requirements into their Product Backlog and Sprint Planning.
✑ It fosters collaboration and alignment among the teams. By integrating their work frequently, they can share their learnings and best practices, and coordinate their efforts towards a common vision and goal. They can also leverage the collective intelligence and creativity of the teams to deliver a better product.
References:
✑ Scrum Guide 2020, page 10: “When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency.”
✑ Scrum Guide 2020, page 10: “The moment a Product Backlog item meets the Definition of Done, an Increment is born.”
✑ Scrum Guide 2020, page 10: “Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together.”
✑ Scrum Guide 2020, page 14: “The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current Definition of Done.”
✑ Scrum Guide 2020, page 15: “The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.”
Who is on the Scrum Team? (choose all that apply)
Correct Answer:
ABC
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a “Done” Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.
References:
✑ The Scrum Guide
✑ The Scrum Team
✑ Professional Scrum Product Owner™ I Certification
What does it mean for a Scrum Team to be cross-functional?
(choose the best answer)
Correct Answer:
B
The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint.
According to the Scrum Guide1, “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint.” This implies that the team does not depend on external resources or specialists to deliver a product increment. The other options do not reflect the true meaning of cross-functionality in Scrum.
1: The Scrum Team | Scrum.org
What typically happens if the Product Backlog is not sufficiently clear at Sprint Planning? (choose the best answer)
Correct Answer:
B
If the Product Backlog is not sufficiently clear at Sprint Planning, the Developers will find it difficult to create a Sprint forecast they are confident they can meet. This is because:
✑ Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint.
The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal.
✑ The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable.
✑ The Product Owner is accountable for ensuring that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must collaborate with the Developers and provide clarifications, feedback, and guidance on what items are most important and valuable for the product.
✑ If the Product Backlog is not sufficiently clear at Sprint Planning, it means that there are items that are not well defined, ordered, or estimated. This may make it hard for the Developers to understand what they are supposed to build and why. It may also make it hard for them to estimate how much work they can do or how long it will take them to do it. This may result in a poor or inaccurate Sprint forecast that may affect the quality or value of the Increment.
Other options, such as the Product Owner selecting the Sprint Goal for the Scrum Team so that work can begin, nothing in particular happening, the Scrum Master not allowing this to happen or looking for a new Scrum Master and re-starting the Sprint, or Sprint Planning being canceled so refinement can be done first, are not valid answers as they do not reflect what typically happens or what should happen in Scrum.
References:
✑ [Scrum Guide], page 14, section “Sprint Planning”
✑ [Scrum Guide], page 7, section “Developers”
✑ [Scrum Guide], page 6, section “Product Owner”
✑ [Scrum Guide], page 11, section “Product Backlog”
