What should happen in sprint planning?
1 min read
Asked by: Kim Tapley
Every sprint planning meeting agenda should include discussions about the ultimate objective of the sprint and the team’s capacity, followed by a granular look at the sprint backlog, before you start slotting tasks into the sprint.
What should be done in sprint planning?
Best practices for running a sprint planning meeting
- Start with the big picture. …
- Present new updates, feedback, and issue. …
- Confirm team velocity and capacity. …
- Go over backlog items. …
- Determine task ownership. …
- Confirm new issues, impacts, and dependencies. …
- Reach a group consensus. …
- Officially begin your sprint.
What should not be considered during sprint planning?
3 Things to Stop Doing During Sprint Planning
- Resizing Carry-Over Product Backlog Items (PBIs) When work is carried over from one sprint to the next, teams often spend a lot of time trying to resize the PBI(s) to accommodate remaining work—but they shouldn’t. …
- Assigning Tasks. …
- Filling Up the Entire Capacity of the Team.
What should I do before my first sprint?
The first sprint
- Start backlog refinement early to prepare the team for sprint two.
- Establish your test approach (test frameworks, process, etc.).
- Ensure that all environments are set up.
- Put any required automation in place (continuous integration, automated releases/deploys, etc.)
