Skip to main content

Sprint goal question

Last post 10:13 am June 28, 2018 by Simon Mayer
4 replies
07:14 pm June 27, 2018

Just to be clear on the topic, ...

When selecting the sprint goal, the team must take into consideration that the goal must be reachable within the sprint lenght right?

Thanks


08:37 pm June 27, 2018

the team must take into consideration that the goal must be reachable within the sprint lenght

In my opinion, that should be one of many considerations in determining a Sprint Goal.

I would not think it is feasible to have "Develop and launch a new mobile credit card system", as there seems to be a tremendous amount of scope that would need to be complete to reach it.

Developing a new feature (i.e. - accepting American Express as a valid payment) might be more achievable.

All of this should be negotiated between the Development Team and the PO to come up with a realistic and achievable goal for the sprint.


10:23 pm June 27, 2018

The Sprint Goal should give the Development Team focus - their guiding North Star - and also provide the Scrum Team with some flexibility.

To expand on Timothy's idea, an example of a Sprint Goal may be to enable customers to make payments on their mobile phones.  And the Product Backlog items selected could be:

  • Pay by credit card
  • Pay by debit card
  • Pay by ACH
  • Pay by check
  • Apple Pay
  • Bitcoin
  • Paypal

Perhaps the Development Team feels that they can forecast the first 5 Product Backlog items, but find out that Bitcoin is going to take much longer because they discovered complications.  They would then renegotiate with the Product Owner, but still meet the Sprint Goal.


04:17 am June 28, 2018

Just to be clear on the topic, ...

When selecting the sprint goal, the team must take into consideration that the goal must be reachable within the sprint lenght right?

Yes. The successful implementation of Scrum depends upon agreeing and meeting Sprint Goals. The team should also bear in mind that the work done to achieve a goal must be of release quality.


10:13 am June 28, 2018

Yes. The successful implementation of Scrum depends upon agreeing and meeting Sprint Goals. The team should also bear in mind that the work done to achieve a goal must be of release quality.

Agreed. Further, I would point out that the whole point of Scrum is giving you something to regularly Inspect & Adapt.

At the end of a Sprint, having met (or failed to meet) a goal, means there are opportunities to make decisions about the future of the product; whether that is a change to the Product Backlog, the team adjusting itself or its processes in some way (e.g. during the Sprint Retrospective), or deciding whether continued investment in the product even makes any sense.

When selecting the sprint goal, the team must take into consideration that the goal must be reachable within the sprint lenght right?

Scrum does not prevent there being a longer term vision, and there being other goals or milestones for the product, which will continue beyond multiple Sprints; but as explained above, the Sprint Goal should be set for a specific Sprint.


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.