The team analyzes its work in a sprint planning meeting. Based on that, the team members plan for the next sprint. In this article at Atlassian, Dan Radigan shares four best practices of a sprint planning meeting.
The To-Do List of Sprint Planning Meeting
More companies and teams are embracing Agile methodology, and so are you. Below are the four best practices of a sprint planning meeting:
Frequently Review the Project Roadmap: Things change a lot within weeks, so keep a close tab on your project roadmap. Ensure the agile team knows about the current epics and versions. These will help in designing the long-term goals of your company.
Conduct a Separate Backlog Meeting: A sprint planning meeting consists of backlog discussion and task mapping for the next sprint. Dedicate a separate 30-minute backlog meeting with the scrum master and the product owner before the sprint meeting.
Keep participation of the entire development team voluntary. This session should prioritize essential work items, ensure a list of well-developed user stories, and update estimates.
Do a ‘silent estimation’ activity with the team to brush up their estimation skills. Use separate columns for each story point value. Team members must categorize the user stories based on values. If there is a disagreement, they can discuss it.
Leverage Data to Make the Most of It: Keep one hour for each week of your sprint. For example, for a two-week sprint, you will have a two-hour sprint planning meeting. Have the meeting in the middle of the week to let the team do their job in peace. The scrum master discusses actionable items while the product owner announces industry highlights. Then, the PO assigns tasks based on team velocity, holiday plans, story priorities, etc. If the team is new, members can agree to a task estimate and monitor their velocity for a couple of sprints. Next, discuss how the team should approach the stories. Assign someone to create meeting minutes continuously.
Ready, Set, Go! At the end of the sprint meeting, verbally confirm that all agree to the next set of tasks. Ensure each member has at least one item, but no two people have the same one. The team spirit will fluctuate throughout the lifecycle. The wise move would be to discuss this during a sprint planning meeting.
To view the original article in full, visit the following link: https://www.atlassian.com/blog/agile/sprint-planning-atlassian