Who is accountable for tracking the remaining work toward the Sprint Goal? (choose the best answer)
Correct Answer:
A
The Developers are the ones who are accountable for tracking the remaining work toward the Sprint Goal. The Developers are self-managing and decide how much work they can do in a Sprint1. They also create and update the Sprint Backlog, which is the plan for how the Developers will achieve the Sprint Goal, and the single source of truth for the work to be done in the Sprint2. The Developers use the Daily Scrum to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. The Product Owner, the Scrum Master, and the Project Manager (if any) do not have the accountability for tracking the remaining work toward the Sprint Goal, as this is the responsibility of the Developers. References:
1: The Scrum Guide, November 2020, p. 6
2: The Scrum Guide, November 2020, p. 10
[3][3]: The Scrum Guide, November 2020, p. 11
What is the timebox for the Sprint Planning event? (choose the best answer)
Correct Answer:
C
✑ The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment.
✑ The timebox for the Sprint Planning event is proportional to the length of the Sprint. For a one-month Sprint, the timebox is 8 hours. For shorter Sprints, the timebox is usually shorter. The Scrum Team may decide how much time to spend on each topic within the timebox, depending on their needs and preferences.
✑ The timebox for the Sprint Planning event ensures that the Scrum Team does not spend too much or too little time on planning their work for the Sprint. The timebox also ensures that the Scrum Team has enough clarity and alignment on what and how they want to achieve during the Sprint.
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning
Which of the following practices might help the Product Owner minimize waste in developing
and sustaining the Product Backlog? (choose the best two answers)
Correct Answer:
CD
The practices that might help the Product Owner minimize waste in developing and sustaining the Product Backlog are:
✑ Remove items from the Product Backlog that have not been addressed in a long time. This helps keep the Product Backlog relevant, concise, and focused on delivering value. Items that have not been addressed in a long time may indicate that they are not important, feasible, or desirable anymore. They may also clutter or confuse the Product Backlog and make it harder to order and prioritize.
✑ Only fully describe Product Backlog items when it seems likely they will be implemented. This helps avoid spending too much time or effort on items that may change or be discarded later. Items that are likely to be implemented soon should have more detail and precision than items that are further away or uncertain. The level of detail and precision required for each item depends on its order, size, and complexity.
Other options, such as avoiding distracting the Scrum Team by maintaining newly gathered Product Backlog items in a separate Product Backlog until they are fully understood or handing off ownership of the Product Backlog to someone else, are not practices that might help minimize waste in developing and sustaining the Product Backlog. They may actually create more waste by reducing transparency, collaboration, alignment, or ownership. References:
✑ [Scrum Guide], page 11, section “Product Backlog”
✑ [Scrum Guide], page 6, section “Product Owner”
✑ [Scrum Guide], page 12, section “Product Backlog Refinement”
Why do the Developers need a Sprint Goal? (choose the best answer)
Correct Answer:
C
The Developers need a Sprint Goal because it gives them a common yet specific goal to focus on during the Sprint. This is because:
✑ The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the 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 Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.
✑ The Developers need a Sprint Goal to align their efforts and collaborate effectively as a team. The Sprint Goal helps them prioritize and optimize their work based on value and impact. The Sprint Goal also helps them cope with uncertainty and complexity by providing a clear direction and a shared purpose.
Other options, such as a Sprint Goal only giving purpose to Sprint 0, Sprint Goals being not valuable, or a Sprint Goal ensuring that all of the Product Backlog items selected for the Sprint are implemented, are not valid reasons why the Developers need a Sprint Goal. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works. References:
✑ [Scrum Guide], page 15, section “Sprint Goal”
✑ [Scrum Guide], page 7, section “Developers”
✑ [Scrum Guide], page 10, section “Definition of Done”
✑ [Scrum Guide], page 10, section “Increment”
True or False: A Scrum Master fulfills the same role as a traditional Project Manager.
Correct Answer:
B
A Scrum Master does not fulfill the same role as a traditional Project Manager. A Project Manager is typically responsible for planning, executing, monitoring, controlling, and closing a project, as well as managing the scope, schedule, budget, quality, risks, and stakeholders of the project1. A Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices, and removes impediments to the team’s progress2. A Scrum Master does not manage the project, the scope, the schedule, the budget, or the team, as these are either shared responsibilities or emergent outcomes of the Scrum framework[3][3]. A Scrum Master also does not have authority over the team or the stakeholders, but rather facilitates collaboration and empowerment among them4.
References:
1: What is Project Management?, Project Management Institute, accessed on December 16, 2023
2: The Scrum Guide, November 2020, p. 7
[3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
4: Developing People and Teams, Scrum.org, accessed on December 16, 2023
