What you'll learn

• How do we demonstrate we make improvements?
• We need baseline, baseline, baseline 
• People measure very often the wrong things, they confuse velocity with productivity 
• Recommended SAFe metrics domains: predictivity, time health, productivity, quality 
• Each domain has its own set of basics
• Understand the difference between leading and lagging indicators  
• Lagging indicators are typically output orientated, easy to measure but hard to improve or influence 
• Leading indicators are input-oriented, hard to measure but easy to influence 
• Team health metrics: staff turnover, sick days, e-NPS, Team and Technical Agility Assessment

Quality metrics: No. of escape defects, mean time of recovery, test automation, code quality.

• Never compare team health agility to another team
• Use the metrics to improve performance not raise competition
• Increasing test automation and static code analytics will help to truck issues before our customers find out it as well

Productivity metrics: Feature Lead Time, Story Cycle Time, Number of Deploys

• Focus on delays

Predictability metrics: Pi program predictability, Program Velocity, No. of features planned, No. of enablers features planned, No. of enablers features accepted, No. of stories planned, No. of stories accepted

Don't forget about the Value metric