Why do the Developers need a Sprint Goal?(choose the best answer)
Answer(s): 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.
[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: The Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal.
Answer(s): A
It is true that the Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal. 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 Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering them as a "Done" Increment. The Sprint Backlog is owned by the Developers who use it to organize and manage their work during the Sprint.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 Sprint Backlog is created by the collaborative work of the entire Scrum Team during Sprint Planning. The Product Owner proposes how the product could increase its value and utility in the current Sprint. The Developers discuss how they can deliver a "Done" Increment that meets this proposal. Together, they define a Sprint Goal that summarizes why the Sprint is valuable to stakeholders. Then, they select enough Product Backlog items from the top of the ordered Product Backlog to satisfy the Sprint Goal. Finally, they create a plan for how they will deliver those items as a "Done" Increment.
[Scrum Guide], page 14, section "Sprint Planning"[Scrum Guide], page 15, section "Sprint Backlog"[Scrum Guide], page 15, section "Sprint Goal"
Scrum requires that the Product Owner must use which of the following items? (choose all that apply)
Answer(s): E
Scrum does not require that the Product Owner must use any of the following items:Burndown chart: A burndown chart is a graphical representation of work left to do versus time. It can be used to track progress and forecast completion dates of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.Feature burn-up: A feature burn-up chart is a graphical representation of features completed versus time. It can be used to track progress and forecast scope changes of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.Critical Path Analysis: Critical Path Analysis is a project management technique that identifies the sequence of tasks that must be completed on time for a project or Sprint to finish on schedule. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.Project Gantt chart: A project Gantt chart is a graphical representation of tasks, dependencies, durations, and milestones of a project or Sprint. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.Therefore, the correct answer is none of the above.
[Scrum Guide], page 6, section "Product Owner"[Scrum Guide], page 11, section "Product Backlog"[Professional Scrum Product OwnerTM Training], page 8, section "Release Management"
When might a Sprint be cancelled?(choose the best answer)
Answer(s): D
A Sprint may be cancelled when the Sprint Goal becomes obsolete. 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 Sprint is a container for all other Scrum events and activities. It is a time-box of one month or less during which a "Done" Increment is created that meets the Sprint Goal. The Sprint has a consistent duration throughout a development effort and only changes duration between Sprints. A Sprint may be cancelled before it is over by the Product Owner if they determine that the Sprint Goal is no longer valid or valuable. This may happen due to various reasons, such as a significant change in the market, technology, business direction, or customer needs. A cancelled Sprint should be rare and exceptional. It implies a waste of time and resources that could have been spent on delivering value. It also disrupts the rhythm and flow of the Scrum Team and the stakeholders.When a Sprint is cancelled, any completed and "Done" Product Backlog items are reviewed and potentially released. Any incomplete Product Backlog items are re-estimated and put back on the Product Backlog. The Scrum Team then plans for a new Sprint. Other options, such as when the Developers determine the product plan is infeasible, when it becomes clear that not everything will be finished by the end of the Sprint, or when the sales department has an important new opportunity, are not valid reasons for cancelling a Sprint. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.
[Scrum Guide], page 15, section "Sprint Goal"[Scrum Guide], page 9, section "Sprint"[Scrum Guide], page 16, section "Cancelling a Sprint"
Post your Comments and Discuss Scrum PSPO-I exam with other Community members:
Barbara commented on October 07, 2024 good content! UNITED STATES upvote
Our website is free, but we have to fight against bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PSPO-I content, but please register or login to continue.