Scrum Updated PSPO-I Exam Questions and Answers by malakai

 The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:

• The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration.
• The timebox for each Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month.
• The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter.
• The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value.

Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.

References:

• [Scrum Guide], page 17, section “Sprint Review”
• [Scrum Guide], page 9, section “Sprint”
• [Scrum Guide], page 9, section “Timeboxing Scrum Events”

To say that an event has a timebox means that the event has a fixed duration that cannot be exceeded. The Scrum Guide states that "All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process."1 This means that the timebox sets an upper limit for the event, but the event can end sooner if the goal is met.

References:

• 1: The Scrum Guide2, page 10
• 2: The Scrum Guide

The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review. This is because:

• The Scrum Team is self-managing and does not need to report to anyone outside the team1.
• The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect the Increment2.
• The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value delivery3.
• The IT manager can attend the Sprint Review as a stakeholder and provide feedback on the product and the process4.

References:

• Scrum Guide, page 7, section “The Scrum Team”
• Scrum Guide, page 13, section “Sprint Review”
• Scrum Guide, page 10, section “Increment”
• Scrum Guide, page 14, section “Sprint Review”

The Scrum Guide states that "The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be ‘Done,’ which means it must be in useable condition and meet the Scrum Team’s definition of ‘Done.’"1 This means that a valuable and useful Increment must be available at the end of every Sprint, regardless of the release frequency or the Product Owner’s request. This ensures transparency, feedback, and continuous improvement.

References:

• 1: The Scrum Guide2, page 14
• 2: The Scrum Guide