Why is the Daily Scrum held at the same time and same place? (choose the best answer)
Correct Answer:D
The Daily Scrum is held at the same time and same place because:
✑ The consistency reduces complexity. By having a fixed time and place for the Daily Scrum, the Developers can avoid wasting time and energy on scheduling, logistics, or coordination issues. They can also establish a routine and a rhythm that helps them focus on their work and their Sprint Goal.
✑ The consistency increases transparency. By having a fixed time and place for the Daily Scrum, the Developers can ensure that everyone is aware of when and where the meeting takes place, and that everyone has an opportunity to participate and share their progress, plans, and challenges. They can also invite other stakeholders or observers, if they find it useful, to provide feedback or support.
✑ The consistency enhances collaboration. By having a fixed time and place for the Daily Scrum, the Developers can create a safe and comfortable space for them to communicate, interact, and collaborate with each other. They can also build trust, rapport, and accountability among themselves, and foster a sense of team spirit and ownership.
References:
✑ Scrum Guide 2020, page 12: “The Daily Scrum is held at the same time and place each day to reduce complexity.”
✑ Scrum Guide 2020, page 12: “The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.”
✑ Scrum Guide 2020, page 13: “The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.”
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”
Every Scrum Team should have: (choose the best answer)
Correct Answer:B
A Scrum Team is a cross-functional, self-managing team that has all the necessary competencies and skills to deliver a potentially releasable Increment of value at the end of each Sprint. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. The Scrum Team does not rely on external roles or hierarchies to complete their work. (Must be taken from Professional Scrum Product Owner™ (PSPO I) resources)
References:
✑ Professional Scrum Product Owner™ I Certification
✑ Professional Scrum Product Owner™ Training
A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for the Product Backlog.
However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog
should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?
• Stability requirements
• Performance requirements
• Product Functionality
• Documentation
• Fixes
(choose the best answer)
Correct Answer:A
✑ The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
✑ All types of requirements are acceptable on a Product Backlog, as long as they are aligned with the product vision and goals, and they are transparent, clear, and valuable. The Product Backlog can include stability requirements, performance requirements, product functionality, documentation, fixes, or any other aspects that contribute to the quality and usability of the product.
✑ 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.
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog
Which three of the following are true about Scrum? (choose the best three answers)
Correct Answer:BCE
The following are true about Scrum:
✑ Scrum is based on empiricism and lean thinking. Empiricism is the principle of making decisions based on what is observed and experienced, rather than on theory or speculation. Lean thinking is the philosophy of eliminating waste and maximizing value in any process or system. Scrum applies these concepts by providing a framework for inspecting and adapting the product and the process, and by focusing on delivering the most valuable features to the customers and stakeholders.
✑ Scrum is a framework for developing and sustaining complex products. A complex product is one that has unpredictable or unknown aspects that require creativity, experimentation, and adaptation to deliver. A framework is a set of minimal and essential rules and roles that provide structure and guidance, but leave room for flexibility and innovation. Scrum provides such a framework for teams to collaborate and deliver complex products iteratively and incrementally, while embracing change and feedback.
✑ Each component of Scrum serves a specific purpose and is essential to Scrum’s success and your usage of Scrum to develop complex products. Scrum consists of three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). Each of these components has a clear definition, accountability, and goal that contributes to the overall effectiveness and value of Scrum. Removing or changing any of these components may cause the benefits of Scrum to be lost or diminished.
References:
✑ Scrum Guide 2020, page 3: “Scrum is founded on empiricism and lean thinking.”
✑ Scrum Guide 2020, page 3: “Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.”
✑ Scrum Guide 2020, page 4: “Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.”