How does a Scrum team decide on a Sprint goal?

Published on
4 minute read

Deciphering the Sprint Goal Enigma 🎯  

The Sprint goal is the North Star for any Scrum team - a beacon that guides the team’s efforts throughout the Sprint. But the million-dollar question remains: How does one conjure this all-important goal?  

If you peek into the Scrum Guide, you might be led to believe it’s a mystical process, but let’s demystify it together. 

Understanding the Sprint Goal  

The Sprint goal is a concise statement of what the team plans to achieve during the upcoming Sprint. It acts as a cohesive element, binding the team with a shared objective. 

The Pre-Planning: Forecasting the Sprint Horizon 🌅  

If you’re stepping into Sprint planning without a clear idea of your Sprint goal, you’re akin to a ship sailing without a compass. The savvy approach? Start the conversation early. During your Sprint review, discuss potential goals with stakeholders. This way, when planning begins, you’re not blind-sided but rather have a direction in mind. 

  • Stakeholder Sync-up: Engage with your stakeholders to gauge their expectations and align them with the team’s trajectory. 

  • Market Pulse: Keep a finger on the pulse of the market to ensure your goals are relevant and timely. 

  • Strategy Alignment: Ensure your Sprint goal dovetails with the broader organisational strategy. 

Crafting the Goal in Sprint Planning 📝 

With the groundwork laid, Sprint planning is where the Sprint goal starts taking shape.  Within the heart of Sprint planning lies the golden moment where the Sprint goal is forged. It’s not just about picking a goal out of the backlog; it’s about shaping an objective that resonates with every member.  

The product owner, with their vision, and the developers, with their technical prowess, must dance a duet that balances aspirations with capabilities. Together, they sketch out a goal that’s not just a to-do list but a strategic move that propels them forward. 

  • Collaborative Crafting: The product owner and development team come together to articulate the goal. It’s about negotiation, discussion, and finally, agreement. 

  • Quantifiable Objectives: The goal must be specific enough to be measurable. A nebulous goal is as good as no goal. 

  • Backlog Alignment: Select backlog items that contribute to the Sprint goal. This alignment ensures focus and purpose. 

Facing the Unpredictable: When the Goalpost Moves 🥅  

Sometimes, despite the best-laid plans, uncertainty strikes. Market changes or stakeholder revelations can turn the Sprint goal on its head. 

  • Agility Over Rigidity: Be prepared to pivot. Agility is at the heart of Scrum. 

  • Time for Teamwork: This is when the collaborative spirit of the team shines. Together, recalibrate and redefine the goal. 

The Art of Decision-Making as a Team 🤝  

Ultimately, deciding on a Sprint goal is a team sport.   Deciding on a Sprint goal is like crafting a treaty; it requires diplomacy, understanding, and, above all, teamwork. It’s about finding that sweet spot where business needs, technical feasibility, and team capacity meet.  

This democratic process ensures that the Sprint goal isn’t a top-down assignment but a team-embraced mission that they’re committed to achieving, with each member’s input valued and considered. 

  • Democracy in Action: Every voice matters. Developers, product owners, stakeholders – all have a part to play. 

  • Consensus is Key: The goal should be something everyone buys into, not a directive handed down from on high. 

Strategies for Success 

To navigate the Sprint goal setting with finesse, teams need strategies as robust as their commitment. Early engagement in goal discussions ensures that when the time comes to formalise the goal, there are no surprises — just clarity and focus. Continuous communication means keeping all channels open so feedback can flow freely and inform adjustments to the goal.  

Lastly, ensuring visibility and clarity of the Sprint goal keeps the entire team aligned, fostering a sense of shared purpose that drives them toward a common finish line. 

  • Early Engagement: Don’t wait for planning to start talking about your next goal. 

  • Continuous Communication: Keep the lines open. Feedback loops are crucial. 

  • Visibility and Clarity: Once decided, make the Sprint goal visible and understood by all. 

A Collaborative Crescendo 🚀  

Deciding on a Sprint goal is a symphony of collaboration, strategy, and agility. It’s about setting a clear, achievable objective that aligns with the team’s mission and the organisation’s vision. When done right, it sets the stage for a Sprint that’s focused, cohesive, and, most importantly, successful.

So the question is how does a Scrum team decide on a Sprint goal? If you were to look in the Sprint guide, it says it just happens, but we all know that’s not going to be true, right? It doesn’t just magically pop into people’s ideas. Some people would attest that the developers and the product owner work together during the Sprint to come up with a Sprint goal, and I would say that’s partially true. I feel like if you walk into your Sprint planning and you don’t already know or don’t already have an idea about what your Sprint goal is going to be, you’re already at a disadvantage.

I would normally discuss what a probable Sprint goal for the next Sprint would be at my Sprint review with my stakeholders. I’d probably be talking about what it is we should be working on next, what does that look like, how does that fit into the strategy? So when I do walk into Sprint planning and we already have an idea which direction we’re going, and then perhaps we’re writing the Sprint goal, right? We have an idea about what it should be, and now we’ve got to get it down on paper. We’ve got to quantify it, and then we’ve got to select the items that go towards it.

I can definitely see circumstances where you walk into Sprint planning and you don’t know up front what it’s going to be. Perhaps stakeholders just dropped a bombshell on you at the Sprint review. Perhaps the market just dropped a bombshell on you at the Sprint review or after. Perhaps you just don’t know yet, right? It’s just too up in the air, and you didn’t know enough, and it’s going to be a really long Sprint planning because we’ve got to figure it out.

But how does the team decide on a Sprint goal? They collaborate between the product owner and the developers with significant input from the stakeholders, with significant input from the market and the business context.

Thanks for watching the video! If you enjoyed it, please like, follow, and subscribe. I always reply to comments, and if you want to have a chat about this or anything else Agile, Scrum, or DevOps, then please book a coffee with me through Naked Agility.

Scrum Product Development People and Process Scrum Team Professional Scrum Agile Planning Scrum Master Team Collaboration Agile Product Management Agile Frameworks Software Development

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Bistech Logo
Teleplan Logo
Higher Education Statistics Agency Logo
Ericson Logo

NIT A/S

SuperControl Logo
Epic Games Logo
Akaditi Logo
Illumina Logo
Boeing Logo
Workday Logo
Deliotte Logo
Freadom Logo
ProgramUtvikling Logo
MacDonald Humfrey (Automation) Ltd. Logo
DFDS Logo
Boxit Document Solutions Logo
Alignment Healthcare Logo
Nottingham County Council Logo
Washington Department of Enterprise Services Logo
New Hampshire Supreme Court Logo
Royal Air Force Logo
Ghana Police Service Logo
Department of Work and Pensions (UK) Logo
Capita Secure Information Solutions Ltd Logo
Cognizant Microsoft Business Group (MBG) Logo

CR2

Microsoft Logo
Trayport Logo
Graham & Brown Logo