Retrospective on being an Agile Coach Scott Bird, Lead Agile Coach October, 2015 My Journey 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 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 Dont Spread Yourself Too Thin Executive Buy In Product Owner Roll Up Impediments Teams Too Big! Burndowns are Critical! Retrospectives need an Action Plan! ? Change Up the Retrospectives! Train teams, not individuals! Be present! Metrics: Are we getting better? Direct Discover Maintain your balance! Stay engaged! Use visual tools! Enterprise support Dont forget tool training! Dont spread yourself too thin! Executive buy in Roll up impediments! Teams too big! And in conclusion Agile is a journey Agile coaching is a journey Any questions? 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 Its their meeting Protects the teamAdvises, but does not protect the team Training vs Coaching TrainingCoaching Finite durationOngoing Knowledge / Skill basedSkill and Competency based Classroom settingOn the job Generalized for all attendeesSpecific to individual / team The Shu of Shu-Ha_RiThe Ha of Shu-Ha-Ri