Skip to main content

Crafting Sprint Goal in end of Sprint planning

Last post 12:15 am January 24, 2019 by Chris Belknap
2 replies
Anonymous
03:22 pm January 23, 2019

I have another basic question 

  • Sprint Goal will be crafted in Sprint planning session by Scrum team 
  • Sprint planning may close even if we plan for initial days of team work may not necessarily identify all the tasks/stories team deliver in entire sprint. 

In above case, how can sprint goal be crafted without knowing entire sprint scope ? 

Please clarify


08:48 pm January 23, 2019

The Scrum Guide does not make any prescription about planning tasks or stories at all. It does say that Sprint Planning addresses two topics, in the second of which the work planned for the first days of the Sprint is decomposed, often to units of one day or less.


12:15 am January 24, 2019

Scrum Guide: The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.

The Sprint Goal provides some wiggle room.  If the Development Team forecasts too many Product Backlog items, or determines that not all the Product Backlog items can be completed based on empirical evidence, they may renegotiate with the Product Owner, as long as they don't endanger the Sprint Goal.

 


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.