1. Retrospective on being an Agile Coach Scott Bird, Lead Agile Coach October, 2015

2. My Journey

3. Agile Implementation: Top Down vs Bottom Up +Consistent implementation +Better coordination across enterprise +Coaches! ∆Expensive ∆Standardization vs Agility +“Sticks” better at the team level +Lower “burn rate” ∆Inconsistent methodologies

4. Anchors and Engines Burndowns are critical! Retros need an action plan! Change up the Retros! Train teams, not individuals! Be present! Metrics! Maintain Your Balance Stay Engaged! Visual Tools Enterprise Support Agile Tool Training Don’t Spread Yourself Too Thin Executive Buy In Product Owner Roll Up Impediments Teams Too Big!

5. Burndowns are Critical!

6. Retrospectives need an Action Plan! ?

7. Change Up the Retrospectives!

8. Train teams, not individuals!

9. Be present!

10. Metrics: Are we getting better?

11. Direct Discover Maintain your balance!

12. Stay engaged!

13. Use visual tools!

14. Enterprise support

15. Don’t forget tool training!

16. Don’t spread yourself too thin!

17. Executive buy in

19. Roll up impediments!

20. Teams too big!

21. »And in conclusion –Agile is a journey –Agile coaching is a journey »Any questions?

22. Scrum Master vs Agile Coach Scrum MasterAgile Coach 1-2 teams2-5 teams Focus on team successFocus on enterprise success Has responsibility for outcomesNot directly responsible for outcome “It’s their meeting” Protects the teamAdvises, but does not protect the team

23. Training vs Coaching TrainingCoaching Finite durationOngoing Knowledge / Skill basedSkill and Competency based Classroom setting“On the job” Generalized for all attendeesSpecific to individual / team The “Shu” of Shu-Ha_RiThe “Ha” of Shu-Ha-Ri