View source | Discuss this page | Page history | Printable version   

Scrum/Stretch goal

Stretch goals - what and why

A stretch goal is a task or story that has been scheduled into a Sprint but that is not committed. It is considered a cherry on top, so a task that the Team hopes to get done in the sprint but isn't absolutely sure they'll get to.

Sometimes teams want to do this because they are really eager to get something done. It also can happen if there are significant tasks in a Sprint that have a high Scrum/Estimations in Story points only because of a high risk. It is therefore seen as a way to avoid having to plan more tasks again when the anticipated risks do not materialize.


As convenient as it is, the practice is interfering with the basic Scrum principle of only committing what you are sure you can do. The main risk therefore is using them to trick the product owner and external stakeholders into the belief that something will be achieved while it will not. If the stretch tasks are added at the request of the team, the risk is they will be treated with higher-than-declared priority. Therefore they pose a risk to the regularly scheduled sprint tasks.

Rules at Openbravo

Retrieved from ""

This page has been accessed 14,170 times. This page was last modified on 12 November 2009, at 15:11. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.