The "cone of uncertainty" can be used to do what?
(choose the best answer)
Correct Answer:
C
✑ The “cone of uncertainty” is a graphical representation of the degree of uncertainty in a project estimate over time. It shows that the range of possible outcomes is wider at the beginning of the project and narrows down as the project progresses and more information becomes available.
✑ The “cone of uncertainty” can be used to illustrate that as a project forecast lengthens, it is increasingly less certain. This means that the longer the time horizon for a project, the more variability and risk there is in the estimate. This also implies that shorter iterations and frequent feedback can help reduce uncertainty and improve accuracy.
✑ The “cone of uncertainty” cannot be used to determine whether to cut quality, similar to the “Iron Triangle” of project management. The “Iron Triangle” is a model that shows the trade-offs between scope, time, and cost in a project. Quality is often considered as a fourth dimension that is affected by these three factors. Cutting quality is not a desirable option for any project, especially for Scrum projects that value delivering high-quality products that meet customer needs.
✑ The “cone of uncertainty” cannot be used to determine the cost of a project before it begins. The cost of a project depends on many factors, such as the scope, the resources, the complexity, the risks, and the market conditions. The “cone of uncertainty” only shows the range of possible outcomes based on the available information at a given point in time. It does not provide a definitive or accurate estimate of the cost before the project starts.
✑ The “cone of uncertainty” cannot be used to determine the length of the next Sprint. The length of the next Sprint is determined by the Scrum Team based on their empirical experience and their ability to deliver a potentially releasable Increment of value. The “cone of uncertainty” does not provide any guidance on how long a Sprint should be or how much work can be done in a Sprint.
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Cone of Uncertainty: https://www.agilealliance.org/glossary/cone-of-uncertainty/
When can Developers cancel a Sprint? (choose the best answer)
Correct Answer:
C
According to the Scrum Guide, a Sprint can be canceled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be canceled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be canceled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense. Developers cannot cancel a Sprint on their own, even if they face challenges or difficulties with the selected Product Backlog items, the functional expectations, the technical dependencies, or the Product Owner’s availability. Instead, they should collaborate with the Product Owner and the Scrum Master to find the best way to deliver value within the Sprint and adapt to the changing situation. References:
✑ The Scrum Guide
✑ Understanding and Applying the Scrum Framework
✑ Professional Scrum Product Owner™ I Certification
A product's success is measured by: (choose the best three answers)
Correct Answer:
ACF
A product’s success is measured by the value it delivers to the customers and the organization. The impact on cost, revenue, and customer satisfaction are three important indicators of value. The Scrum Guide states that "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."1 The Product Owner should consider the cost of developing and maintaining the product, the revenue generated by the product, and the satisfaction of the customers and users who use the product. These factors help the Product Owner to prioritize the Product Backlog, define the Product Goal, and collaborate with the stakeholders.
References:
✑ 1: The Scrum Guide2, page 6
✑ 2: The Scrum Guide
In the middle of the Sprint, the customer decides that there are two new features she wants.
The Product Owner could: (choose the best two answers)
Correct Answer:
BC
✑ The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
✑ The Developers 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.
✑ A Sprint is a timebox of one month or less within which a “Done” product Increment is created. A Sprint consists of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. A Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process.
✑ The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint.
✑ In the middle of a Sprint, if a customer decides that there are two new features she wants, there are two possible ways that a Product Owner could handle this situation:
✑ The other options are not valid or relevant ways that a Product Owner could handle this situation. They are either too disruptive, impractical, or irrelevant. They are:
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
✑ Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
✑ Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum
✑ Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal
✑ Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum
✑ Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
Why does the Product Owner want the Developers to adhere to its Definition of Done? (choose the best answer)
Correct Answer:
B
The Product Owner wants the Developers to adhere to its Definition of Done to have complete transparency into what has been done at the end of each Sprint. This is because:
✑ The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what “Done” means for any Product Backlog item that is selected for a Sprint.
✑ The Developers are accountable for creating a “Done” Increment in every Sprint.
They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
✑ The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.
✑ Having a clear and consistent Definition of Done helps the Product Owner have complete transparency into what has been done at the end of each Sprint. It also helps them make informed decisions about releasing, adapting, or continuing the product development.
Other options, such as predicting the team’s productivity over time, knowing what the team will deliver over the next three Sprints, or reprimanding the team when they do not meet their velocity goal for the Sprint, are not valid reasons for wanting the Developers to adhere to its Definition of Done. They may reflect a misunderstanding of what a Definition of Done is or how Scrum works.
References:
✑ [Scrum Guide], page 10, section “Definition of Done”
✑ [Scrum Guide], page 7, section “Developers”
✑ [Scrum Guide], page 6, section “Product Owner”