Day 185. Read the title as ‘… Increasing Predictability With Objectives… Without Specifying THE MEANS!’ I intentionally wrote the title as you see it now
Day 183. For some reason, a LOT of people find writing PI Objectives hard: they struggle… they are unsure… and… after a lot of thought…
Day 90. A PI Roadmap is actually not a roadmap containing Features per se. Instead, it contains events and the PI Objectives — both committed
Day 89. PI Planning: one of the outputs is the team’s PI Objectives. How to write these? Tip: focus on the desired outcome… and write
Day 76. Scrum of scrums is a SAFe program-level event that is geared toward synchronization between scrum masters of the Agile Release Train; it’s facilitated
Tip on synthesizing planned work into PI objectives: Find the ‘Deep meaning’ (the intent). Try this: stand back and look at, holistically, the planned work.
Program Increment (PI) Objective is mysterious and troublesome to some folks. What is it? How is it written?Where is it from? What is it for?
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
A goal with a strong ‘Why’ will not only pulls you forward but also pulls you through difficult times. Make your ‘Iteration Goals’ and your
Intent is a ‘broad stoke of the brush’ kind of sketch of what you want to achieve… without providing instructions on how to achieve it…
Everyone has a purpose (an intent of what to accomplish (i.e. ‘CI = Commander’s Intent’ In the military realm) in mind on what to do
We have covered iteration goals and PI objectives… but forgot to put forth two key things to the forefront … it has been on the