Scrum events and timeboxes: Sprint Planning to Retrospective

Try 3 questions on this

Pick an answer to see why each option is right or wrong.

1. Key stakeholders attend every Sprint Review but mostly watch while the Developers demonstrate features. The project manager wants their input to shape the Product Backlog. Which of the following should the Sprint Review become?

   Right. In the game that’s Renown for your People building.

   Not that one: D is right. In the game your People building would lose a little Renown, and this question would come back later.

   Your answerA.A follow-up stakeholder feedback surveyA survey after the event gathers views separately, while the Sprint Review is where attendees decide together.Your answerB.A detailed written progress reportA written report informs stakeholders but replaces inspection and collaboration with one-way reporting.Your answerC.A rehearsed demo with closing questionsAdding questions at the end looks like it invites input, but it keeps the event a presentation, which the Scrum Guide tells the team to avoid.The answerD.A collaborative working sessionThe Scrum Guide calls the Sprint Review a working session and says the Scrum Team should avoid limiting it to a presentation. The Scrum Team and stakeholders review what was accomplished and what has changed, and the attendees collaborate on what to do next.

   Written from scrumguides.org/scrum-guide.html

2. Midway through a Sprint, the Developers find one selected item is far larger than forecast, so not every selected item will be finished. Which of the following should the project manager encourage?

   Right. In the game that’s Renown for your People building.

   Not that one: A is right. In the game your People building would lose a little Renown, and this question would come back later.

   The answerA.Renegotiate scope with the Product OwnerThe Scrum Guide says that during the Sprint, scope may be clarified and renegotiated with the Product Owner as more is learned, without endangering the Sprint Goal and without lowering quality.Your answerB.Extend this Sprint by a weekA Sprint has a fixed length of one month or less; the Scrum Guide does not stretch it to fit the work.Your answerC.Have the Developers drop the itemThe Sprint Backlog is the Developers' plan, so dropping an item themselves feels like self-management, but scope changes during the Sprint are renegotiated with the Product Owner.Your answerD.Reduce testing on that itemDuring a Sprint quality does not decrease, so cutting testing to fit the work is ruled out.

   Show the full explanation and doc quotes

   When work turns out different than expected, the Developers collaborate with the Product Owner to negotiate the Sprint Backlog's scope.

   Written from scrumguides.org/scrum-guide.html

3. This Sprint, the Product Owner is also building two items in the Sprint Backlog. The Scrum Master suggests the Product Owner stay away from the Daily Scrum so the Developers can self-manage. Which of the following should the project manager encourage?

   Right. In the game that’s Renown for your People building.

   Not that one: B is right. In the game your People building would lose a little Renown, and this question would come back later.

   Your answerA.Staying away from the eventStaying away fits a Product Owner with no Sprint Backlog work; one who is building items participates as a Developer.The answerB.Joining it as a DeveloperThe Daily Scrum is an event for the Developers, but the Scrum Guide says that if the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.Your answerC.Getting updates from the DevelopersLeaves the Product Owner's own Sprint Backlog work out of the team's daily inspection and plan.Your answerD.Attending only to answer questionsThe Product Owner is doing Sprint Backlog work, so they take part as a Developer, not as someone answering questions.

   Show the full explanation and doc quotes

   This Product Owner is building two items, so they take part as a Developer.

   Written from scrumguides.org/scrum-guide.html