Product resources
Sprint Planning with Easy Agile TeamRhythm
The main purpose of sprint planning is to determine which user stories or backlog items will be worked on, discuss the scope and define the sprint goals to establish a shared understanding.
Purpose and objective of sprint/version planning
Sprint planning is a crucial activity within the agile framework, specifically in Scrum methodology. It is a collaborative process that allows the development team, scrum master, and product owner to come together and plan the upcoming sprint. The main purpose of sprint planning is to determine which user stories or backlog items will be worked on, discuss the scope and define the sprint goals to establish a shared understanding.
Here are some key aspects:
- Establishing sprint goals
- Prioritizing work
- Breaking down user stories
- Estimating effort
- Collaborative decision-making
- Commitment and accountability
Key users (roles & responsibilities)
- Development team: Responsible for implementing work during the sprint, actively participating in sprint planning by contributing expertise, estimating effort, and breaking down user stories into tasks.
- Scrum Master: Facilitates the sprint planning meeting, ensuring correct process adherence, and removing obstacles to team progress. Guides the team through planning activities.
- Product Owner: Actively engages in sprint planning, providing insights into the product backlog, answering questions, and assisting with user story prioritization. Holds final decision-making authority for sprint content and priorities.
It is important to note that while the development team, scrum master, and product owner are the primary audience for sprint planning, other stakeholders or interested parties may also be involved, depending on the specific project and organizational context.
Sprint planning with Easy Agile TeamRhythm
User goal
As an agile software development team, our goal is to effectively plan the upcoming sprint by considering our capacity and establishing a shared understanding of a common goal.
Scenario
On the first day of Sprint 2, the whole team meet to plan to create their plan.
- Close off Sprint 1
- Set a sprint goal
- Access a view of work on the backlog you can draw from
- Apply a filter to shape what they see on the story map
- Use drag and drop or quick actions to schedule the work into the sprint
- Re-estimate tasks if needed & review estimate totals to assess commitment
- Assign issues to owners for initial work
- Assess and edit the goal if needed
- Start the sprint
