Predictability
Over and above a team’s velocity, it is sometimes preferable to have the ‘predictability’ of the teams and ensure that the objectives have been understood, analysed, conceptualised, documented, developed, tested and delivered (realised).
Predictability enables me to ensure that the teams are working together properly and are able to communicate.
Measurement is simple:
- At the start of an iteration (sprint planning or PI Planning), the PO sets the business value (on a scale of 0 to 10) for the committed objectives – committed value.
- At the end of the iteration (review/demo), the PO assesses the business value of the objectives achieved (value is added to objectives not committed) – observed value.
- Predictability is the ratio of observed value to committed value.
Predictability is of interest at all levels of a programme. Whether at the level of each team, or at the level of several teams.
The level of predictability should increase with the life of the team. It is generally accepted that predictability cannot be stabilised before several iterations, depending on the complexity, the level of inter-individual knowledge of the team members and the mastery of the functional and technical perimeters.
Ref
Metrics on SAFe: scaledagileframework.com/metrics/
