Maximize Your Leadership Potential
Leadership isn’t a journey you should take alone. What if you had someone to come alongside you? I provide coaching to help you reach your vision, lead others and grow as a leader.
It’s the first day of a new sprint! There’s some excitement in the air. The whole team works together to plan the sprint. They have the sprint goal and the backlog, but..
What actually happens in sprint planning?
This article will show you the value of sprint planning and how to practice it well. I will walk through three essential concepts for running your sprint planning session.
- Sprint planning provides focus and clarity for the team to reach the sprint goal together.
- Understand how the whole Scrum team participates in sprint planning.
- Outline a simple agenda for you to run sprint planning.
Sprint planning provides focus and clarity for the team to reach the sprint goal together.
The product owner sets the sprint goal, providing direction and communicating what value the team will deliver in this sprint. The sprint goal isn’t prescriptive to how the team will work during the sprint, but it focuses on what must be true when the sprint ends. The goal should also clarify how this sprint builds on the previous sprint.
As the sprint begins, work moves from the product backlog (all the defined work to be done for the product) to the sprint backlog (just what will be done during the sprint). Because work doesn’t get added mid-sprint, the team can focus just on what is in the sprint backlog. There is a sense of urgency to get that work done and a sense of safety that new work and priorities won’t become obstacles to what they’ve selected.
The sprint goal isn’t prescriptive to how the team will work during the sprint, but it focuses on what must be true when the sprint ends.
During sprint planning, the development team plans how to complete the selected work. They communicate this plan to the product owner and scrum master. There’s something about saying a plan out loud to someone else that elevates your focus and commitment, as well as helping to identify gaps.
Understand how the whole Scrum team participates in sprint planning.
Planning the sprint is a collaborative process, and each part of the Scrum team has a role to play.
The product owner sets the direction at sprint planning.
The sprint goal outlines what value the product owner has prioritized for the sprint. While communicating the sprint goal, they will connect it to the previous sprint and probable work for the next sprint.
The product owner stays present throughout sprint planning to answer any questions from the rest of the team. They are also present at the end to hear the team's plan.
The development team owns how to get the work done during sprint planning.
The sprint goal tells the team what to do but not how to do it. The development team owns completing the work together and plans how to complete the work together. The team considers who has the skills or knowledge for each product backlog item. They may decide to each take a different part, or they may all swarm around one or two items initially and then decide who will take the remaining items.
The plan helps the team focus and strategize, but they can adjust it as needed. This adjustment happens daily in the standup as the team checks in. They make their progress visible, evaluate where they are and where they need to go and adjust the plan accordingly.
The scrum master provides sprint planning facilitation as needed.
As the dev team plans the sprint, the scrum master is there to help. If the team is getting stuck on what order to tackle what’s in the backlog, the scrum master can remind them they just need to choose how to start because they can adjust as they go. If the team is concerned about a specific PBI or about getting all the work done, then the scrum master may facilitate a pre-mortem to help them identify how the sprint could go awry and plan accordingly.
It’s easy to go overtime in planning, hoping to get everything just right. The Scrum Master helps the team keep to their timebox limit for the meeting, reminding them that they will meet tomorrow for standup and can continue to adjust if needed.
Scale Your Impact
What if it took the same amount of work to engage and serve 100 people as it would for 10? Let’s map out your workflows and processes and then adapt them in order to impact others at scale.
Outline a simple agenda for you to run sprint planning.
The agenda for sprint planning is pretty straightforward, and the primary challenge is not to go overtime on any of the parts. In general, the sprint planning should be limited to 2 hours for every week the sprint is long.
Sprint Goal [20%] Product owner sets the direction for the sprint. The team identifies which PBIs to pull from the product backlog to the sprint backlog.
Planning [70%] Team makes a plan for how they will complete the selected work. This includes setting an initial order and who will tackle what. It also includes identifying dependencies or needed learning for selected work.
Recap [10%] The team communicates their plan back to the product owner and scrum master.
Getting started with Sprint Planning
I hope this article provided helpful guidance to run efficient and effective sprint planning sessions. If you want to learn more about Scrum in general, To learn more about Scrum, check out my What is Scrum? A Guide for Everyday People to Learn Scrum. If you have more questions, please feel free to reach out on LinkedIn.
Still not sure about your next step with Scrum? I offer a couple of free coaching sessions each month. You can signup for a free 1-hour coaching session, and we can work together to identify a good next step for you.
Maximize Your Leadership Potential
Leadership isn’t a journey you should take alone. What if you had someone to come alongside you? I provide coaching to help you reach your vision, lead others and grow as a leader.
This post is part of an upcoming guide called Everyday Scrum? A Guide for Everyday People to Learn Scrum where I will explore and explain the key elements of Scrum.
Perhaps you have heard about Scrum but are not exactly sure what it is. Or maybe you know some about it but are not sure how to apply it, especially outside a software development context.
You find my my current and future guides on everyday.design. Signup to be the first to know when new guides are released.
There are a lot of new terms when learning the Scrum essentials, and this post probably introduced you to some of the vocabulary.
If you want to learn more about specific Scrum topics, here are a few to choose from or check out the scrum FAQs.
Applying Scrum
- How do I keep my team focused on the right work?
- What to do when projects change?
- Getting work done as a team
- How to change direction after investing effort?
Agile in Everyday Life
- Can I use Scrum for non-software development projects?
- Scrum for marketing
- Scrum for creative design
- Scrum in content creation
- Scrum in personal development
- Scrum in education
- Scrum in everyday home projects
Scrum Roles
- What is a Scrum Product Owner?
- What does a Product Owner do each day?
- Getting Certified as a Product Owner
- What is a Scrum Master?
- What does a Scrum Master do each day?
- Getting Certified as a Scrum Master
- Can The Scrum Master And Product Owner Be The Same Person
- How Is A Scrum Master Different Than A Project Manager?
Scrum Meetings
- How to do a standup/check-in?
- How to do sprint planning in Scrum?
- How does backlog refinement work in Scrum?
- What is a sprint review in Scrum?
- How to conduct a retrospective in Scrum?
Scrum General Topics
- Why Use Scrum?
- What Is The Definition Of Scrum?
- What Are The Pros & Cons Of Scrum?
- Scrum: Expectations Vs. Reality
- Is Scrum Hard To Learn?
- How To Align The Scrum Values With Your Organizational Culture
- What's the difference between iterative and incremental development?
- What Is The Definition Of Done In Scrum?
Scrum Advanced Topics
- Learn To Forecast Progress In Scrum
- What If I Don't Have All The Roles In Scrum?
- Scaling Using SAFe
- Cost Estimation
To learn more about Scrum, check out my What is Scrum? A Guide for Everyday People to Learn Scrum. If you have more questions, please feel free to reach out on LinkedIn.
FAQs
Scrum events overview
What are the Scrum events?
Sprint planning, daily standup, backlog refinement, sprint review, sprint retrospective.
The rhythm of scrum consists of various events.
- Sprint planning
- Daily standup
- Backlog refinement
- Sprint review
- Sprint retrospective
- The sprint
The last on the list is sometimes debated as to whether or not it’s actually a scrum event. I include it because it's critical to creating a cadence of work for the team.
Learn more about the rhythm of scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
What scrum events are timeboxed?
Every Scrum event is timeboxed.
Most scrum events are timeboxed relative to the length of the sprint:
- Sprint planning: 2 hours / sprint week.
- Daily standup: 15 minutes.
- Backlog refinement: 2 hours / sprint week.
- Sprint review: 1 hour / sprint week.
- Retrospective: 45 minutes / sprint week.
Just because an event has a timebox doesn’t mean it needs to be that long. The timebox is the maximum time allowed for the event.
Learn more about the different scrum events. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
When should scrum events be held?
The Scrum team has freedom to adapt when some of the Scrum events are held.
Scrum events are generally held in the following order
- Sprint planning: Held at the very beginning of a sprint.
- Daily standup: Every day at the same time and place.
- Backlog refinement: Flexible. Held at whatever time and frequency best serves the team.
- Sprint review: Held on the last day of the sprint.
- Retrospective: Very last event of the sprint.
The backlog refinement session is unique in that it can be held anytime.
Explore further the events of scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Which scrum event is most important?
Trick question...
I included this because it is frequently asked, but the question misunderstands the importance of the scrum events. It’s like asking which of your limbs is most important. You may be able to answer, but they are really all critical.
If pressed for an answer, the daily scrum probably has the greatest impact on the team's effectiveness.
Learn more about the events in scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Beginning a sprint
What is sprint planning in scrum?
Sprint planning is the first event of the sprint and provides clarity for the team to reach the sprint goal.
Here’s a quick agenda
- Product owner sets the sprint direction.
- PBIs move from the product backlog to the sprint backlog.
- Team plans how they will complete the selected work.
- Team communicates their plan back to the product owner and scrum master.
Learn more about how to facilitate sprint planning. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
What is a sprint in scrum?
A sprint is the basic unit of time in scrum, serving as a boundary for what the team focuses on.
Think of scrum as a relay race, with each sprint being a lap. The scrum team hands off the “baton” of finished work to itself in the next sprint.
Learn more about the role of a sprint in scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Is the sprint a scrum event?
The sprint contains all the Scrum events.
The sprint isn’t always included in the list of scrum events. I include it because it's critical to creating a cadence of work for the team. The sprint serves as a container for all other scrum events.
Learn more about sprints in scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
At which scrum event is the sprint backlog created?
Sprint planning.
The sprint backlog is created during sprint planning as PBIs (product backlog items) are moved from the product backlog to the sprint backlog.
Learn more about the sprint planning process and then explore the most common terms in a Scrum glossary.
Facilitating scrum events
How to facilitate scrum events?
Facilitation is customized to the event and the needs of the team.
Scrum events have a clear purpose and agenda but are still very interactive. Facilitation of scrum events is at its best when everyone is engaged, asking or responding to questions. All events are timeboxed, so the facilitator must ensure the team is always moving toward the goal.
Learn more about team member's responsibilities during scrum events. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
How to improve scrum events?
Scrum events improve as participation increases.
Three strategies for increasing participation in scrum meetings are
- Clearly state the goal. Sometimes people don’t engage because they are unsure about the purpose.
- Use facilitation games. There are many facilitation exercises available for the scrum events.
- Invite feedback. Inspection is a pillar of scrum. Ask the team for feedback on what went well and how to improve.
Learn more about everyone’s roles and responsibilities during the scrum events. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Who facilitates (or owns) scrum events?
Different members of the Scrum team facilitate the various Scrum events.
Scrum cultivates shared ownership for all the events, but each still has a facilitator.
- Sprint planning: Scrum master.
- Daily standup: Development team.
- Backlog refinement: Product owner.
- Sprint review: Product owner.
- Retrospective: Scrum master.
Learn more about everyone’s roles and responsibilities during the scrum events. Then explore the most common terms in a Scrum glossary and learn what is Scrum.
Does the scrum master facilitate all the scrum events?
The Scrum Master primarily facilitates sprint planning and the retro.
The scrum master primarily facilitates two scrum events:
- Sprint planning
- The retrospective
The scrum master can help facilitate other meetings while a new team is beginning to learn scrum.
Learn more about roles during scrum events. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum events purpose
What is the goal of each Scrum event?
Each event has a clear purpose.
- Sprint planning: Clarify the direction and goal for the sprint.
- Daily standup: Everyone on the team gains updated visibility into everyone’s work.
- Backlog refinement: Understand upcoming work.
- Sprint review: Present finished work to stakeholders for feedback.
- Sprint retrospective: Review how the team works and make necessary adjustments.
Understand the purpose of the scrum meetings. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Which scrum events facilitate inspection and adaptation?
Every event includes inspection and adaptation.
Inspection and adaptation (along with transparency) are pillars of scrum, so all events involve them.
- Sprint planning: the purpose and work of the sprint are inspected.
- Daily standup: progress toward the sprint goal is inspected, and adjustments are made.
- Backlog refinement: upcoming work is inspected, and PBIs are adapted.
- Sprint review: delivered work is inspected, and upcoming work is adapted
- Retrospective: team health and interactions are inspected, and norms or plans are adapted.
Learn more about the role of events in scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Which scrum event is for process improvement?
Each Scrum event plays a role in process improvement.
Process improvement aligns closely with the scrum pillars of transparency, inspection and adaptation.
- Sprint planning: How do we improve the product?
- Daily standup: How do we improve our approach to the sprint goal?
- Backlog refinement: How do we improve the quality of the product backlog?
- Sprint review: How do we improve the functionality being delivered?
- Retrospective: How do we improve how our team works together?
Out of all the events, the retrospective is the most focused on process improvement.
Learn more about events in scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
What is the goal of the scrum of scrum event?
Coordinating between multiple Scrum teams focused on the same product.
The scrum of scrums is an extra scrum event used when multiple scrum teams are collaborating together on a single product. The session allows the teams to update each other on what has been done, what obstacles have been encountered, and what to do next. The scrum of scrums follows a similar pattern to the daily scrum session.
To learn more explore the most common terms in a Scrum glossary.
