Skip to content

Commit

Permalink
Fix: minor remaining findings
Browse files Browse the repository at this point in the history
  • Loading branch information
danieldanielecki authored May 22, 2023
1 parent 5d7722b commit 4490ce9
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1526,7 +1526,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
### In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach a clear understanding about the highest order Product Backlog items. Because of this, the Development Team couldn't figure out how many Product Backlog items it could forecast for the upcoming Sprint. They were able to agree on a Sprint Goal, however. Which of the following two actions should the Scrum Master support? (choose two)

- [ ] Cancel the Sprint. Send the entire team to an advanced Scrum training and then start a new Sprint.
- [x] Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze,decompose, and create additional functionality during the Sprint.
- [x] Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint.
- [ ] Continue the Sprint Planning meeting past its time-box until an adequate number of Product Backlog items are well enough understood for the Development Team to make a complete forecast. Then start the Sprint.
- [x] Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.
- [ ] Ask everyone to take as much time as needed to analyze the Product Backlog first, and then reconvene another Sprint Planning meeting.
Expand Down Expand Up @@ -2485,7 +2485,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n

- [ ] The Product Owner can help clarify or optimize the Sprint when asked by the Developers.
- [ ] The Developers may work with the Product Owner to add or remove work if they find themselves with more or less capacity than expected.
- [x] The Sprint Backiog is fully formulated in the Sprint Planning event and does not change during the Sprint.
- [x] The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.
- [ ] As a decomposition of the selected Product Backlog items, the Sprint Backlog changes and may grow as the work emerges.

**[⬆ Back to Top](#table-of-contents)**
Expand Down

0 comments on commit 4490ce9

Please sign in to comment.