SAFe 5.0

Bye ‘Stretch Objectives’

Hello ‘Uncommitted Objectives’!

SAFe makers recognized that a lot of people got tripped by the word ‘Stretch’… so they’ve replaced it with ‘Uncommitted’… just to make clearer the same intent: knowing that the work is important (could be very or most important), the team will do the best they can — capacity will be allocated; still part of the plan; included in the team’s load for the PI (Program Increment) — but will not be penalized if not achieved… this situation happens when there are too much unknowns… impossible to commit to… but it is not a case of ‘just in case the team got time to do it’. This mechanism — putting unpredictable work to the ‘uncommitted objective’ category– enhances the agile team’s program predictability measure by balancing planned committed work and planned uncommitted work.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s