What are two effective ways for the Scrum Team to make non-functional requirements visible?
(choose the best two answers)
Correct Answer:
AC
Non-functional requirements are the criteria that define the quality, performance, security, usability, and other aspects of a product1. They are often implicit or assumed, but they are important to make visible and explicit, as they affect the value and satisfaction of the product2. One effective way to make non-functional requirements visible is to add them to the Product Backlog, which is an ordered list of everything that is known to be needed in the product[3][3]. By adding non-functional requirements to the Product Backlog, the Product Owner and the Developers can prioritize, refine, and estimate them, and make them transparent to the stakeholders4. Another effective way to make non-functional requirements visible is to add them to the Definition of Done, which is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done5. By adding non-functional requirements to the Definition of Done, the Developers can ensure that every Product Backlog item and Increment meets the expected quality standards, and that the work is taken care of every Sprint.
References:
1: Non-functional requirement, Wikipedia, accessed on December 16, 2023
2: Managing Products with Agility, Scrum.org, accessed on December 16, 2023 [3][3]: The Scrum Guide, November 2020, p. 6
4: The Scrum Guide, November 2020, p. 7
5: The Scrum Guide, November 2020, p. 13
Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
You are the Scrum Master of a new, to be developed Product. Development is going to require 45 people. What is a good first question for you to suggest the group thinks about when forming into teams?
(choose the best answer)
Correct Answer:
D
When forming a Scrum team, it is important to ensure that the team has all the skills and knowledge necessary to deliver a working product12. The Scrum team should be cross-functional and self-managing, without relying on external experts or team leads34. Therefore, the question of how to make sure all teams have the right amount of expertise is a good first question to consider when forming into teams.
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
