Back to Forum

How to decide the Sprint Goal in the very 1st sprint?

Last post 05:38 pm August 29, 2019 by Tony Divel
2 replies
SUMIT AGRAWAL
05:18 pm August 29, 2019

Scenario - 

As its a very first sprint, no past reference data is available in terms of CLIENT FEEDBACK or VELOCITY.

So on what basis Scrum Team picks up the number of stories to work upon?

Steve Matthew
05:21 pm August 29, 2019

So on what basis Scrum Team picks up the number of stories to work upon?

Based on the Sprint Goal.

First sprint or N'th Sprint doesn't matter, the Product Owner ideally should have a Goal that they'd like to achieve each Sprint, to realize value through customer feedback. 

Tony Divel
05:38 pm August 29, 2019

Ideally the team would delivery at least one piece of working functionality. 

I've worked with a team who took the first Sprint to build out the Product backlog a little more, run some experiments to flush out risks, and create an initial Product Roadmap. 

This was set up as the Sprint Goal and was achieved by the team. Overall everyone was happy because we could get feedback on the roadmap, risks, and upcoming work. This also positioned them for more effective planning and review sessions going forward. 

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.