Skip to main content

Sprint goal is not about increment but its value

Last post 11:28 am August 12, 2021 by Balaji Dhamodaran
No replies yet
11:28 am August 12, 2021

There are lot of questions in the agile community about how to frame a sprint goal. It can't be like 'completion of all items in sprint backlog' or when working on stories which are part of different features/applications, it can't be like 'enabling the search filter facility plus adding a new product to ecommerce category and so on..'

The reason for confusion is I think we are trying to tag the sprint goal to 'what' part of the sprint and not to the 'why' part. Why is this sprint valuable ? whats the goal to achieve and why?  So the goal could be target increase in value to the product?(how the value is measured is upto your organisation). Increase in customer base by 10% or solving the long pending problem in some business process ? Thats what stakeholders need right ?. Product Owner explains how the increment could increase the value. So the team collaborates to define Sprint goal to achieve the desired value. 

 


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.