Agile Retrospectives for Business Agility

Notes from the Scrum Alliance webinar, “Agile Retrospectives for Business Agility”

• see “Agile Retrospectives: Making Good Teams Great”

5 W’s of restrospectives

• Who
• Why
• What
• When
• Where

Who

facilitator defines who

if sprint retro, should only include scrum team, not managers

Why

means to inspect, adapt, and continually improve

What

What went well, what could have gone better

When

depends on focus of retro; could be every sprint, quarterly, etc

Where

neutral space

6 Step Retrospectives (ODDPAC)

based on 5 steps from book above

1. Open and set the scene activities
   • two words that describe iteration
2. gather Data activities
   • plus/delta: plus is what went well; delta is what didn’t
   • radar/spider chart
   • have everyone rate on a 5-point scale the success of each of the vertices
   • see screen shot ? could we standardize on this and compare across teams?
   • outside of sprint retros, can use different axises; like the priority roles from the 7 Habits of Highly Effective People
     • especially for individual retros

-3 little pigs - different way of categorizing

1. Discuss and group like items

2. identify Priority items and create actionable tasks

3. make visible to hold each other Accountable
   • SMART actions
   • include assignee and due date
4. Close the retro
   • meta retro: how did the retro go and what could we do better