![Sample Iteration Planning AgendaProduct Vision and Roadmap [Product Owner]Development status, state of our architecture, results of previous iterations [Team members] Iteration name and theme [ScrumMaster]Velocity in previous iteration(s) [ScrumMaster]Iteration timebox (dates, working days) [ScrumMaster] Team capacity (availability) [Team members]Issues and concerns? [ScrumMaster]Review and update definition of Done [Team Members]Stories/items from the backlog to consider [Product Owner]Tasking out [Agile Team]Issues, Dependencies & Assumptions [ScrumMaster]Commit! [Agile Team]](https://image.slidesharecdn.com/switchkeynote-101001154642-phpapp01/75/3-Steps-to-Leading-a-Successful-Agile-Rollout-29-2048.jpg)
Uploaded byZach Nies
3 Steps to Leading a Successful Agile Rollout
The document outlines 3 steps to a successful Agile rollout: 1) Direct the Rider by motivating people using concrete examples and celebrating small wins, 2) Motivate the Elephant by addressing fears and building new habits, and 3) Shape the Path by establishing an environment that supports the new process. It provides tips for each step such as grooming backlogs, using standup meetings, and publicizing successes. The overall goal is a smooth transition to Agile working by addressing both rational and emotional aspects of change.
More Related Content
Similar to 3 Steps to Leading a Successful Agile Rollout
3 Steps to Leading a Successful Agile Rollout
- 1. 3 Steps toLeading aSuccessful Agile Rollout
- 2.
- 3.
- 4.
- 6. Direct the RiderMotivatethe ElephantShape the Path
- 7. 3 steps toa successful agile rolloutDirect the RiderMotivate the ElephantShape the Path
- 8. SuccessReduced time-to-marketIncreased qualityReducedwasteBetter predictabilityBetter moraleForrester Research analyst Carey Schwaber, 8/28/07
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. Direct the RiderMotivatethe ElephantShape the Path
- 23.
- 24.
- 25. Who else isdoing Agile?http://www.flickr.com/photos/nicmcphee/103783787
- 26.
- 27. How Do YouGet Started?
- 28. Backlog GroomingStandupDemo /Review & RetrospectiveIteration PlanningIterationIteration BacklogProductBacklogProductIncrementScrum Framework
- 29. Sample Iteration PlanningAgendaProduct Vision and Roadmap [Product Owner]Development status, state of our architecture, results of previous iterations [Team members] Iteration name and theme [ScrumMaster]Velocity in previous iteration(s) [ScrumMaster]Iteration timebox (dates, working days) [ScrumMaster] Team capacity (availability) [Team members]Issues and concerns? [ScrumMaster]Review and update definition of Done [Team Members]Stories/items from the backlog to consider [Product Owner]Tasking out [Agile Team]Issues, Dependencies & Assumptions [ScrumMaster]Commit! [Agile Team]
- 30.
- 31.
- 33. Agile Rollout for50033
- 34. Metrics aren’t thedestination
- 35. Direct the RiderMotivatethe ElephantShape the Path
- 36.
- 37. No more deathmarcheshttp://www.flickr.com/photos/elcapitan/2387917709
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48. Direct the RiderMotivatethe ElephantShape the Path
- 49.
- 50. Take over aconference roomhttp://www.flickr.com/photos/jnicho02/2510307005
- 51.
- 52.
- 53.
- 54. RetrospectivesWhat HYPOTHESES couldwe draw about how we move forward?What has HELPED us?What has HINDERED us?
- 55.
- 56.
- 57. Host a lunchandlearnhttp://www.flickr.com/photos/rubynuby/3573428078
- 58. Direct the RiderMotivatethe ElephantShape the Path
- 59.
- 60.
- 61. How to bean ExpertExpert –Always In Flow“I will keep pushing myselfThere is always a better way”ExpertKick-AssThresholdAbilityAmateur“Now that I can do this,I will just keep doing it this way”SucksThresholdDrop-outStruggling/Frustrated“I suck at thisI give up!”TimeFirst TimeYears/ DecadesKathy Sierra – “Creating Passionate Users”
Editor's Notes
- #11 Let’s learn more about our brains
- #24 Find the pockets of success and replicate.
- #26 Listen, interview and find out what works.Not everything is broken.
- #27 Find the pockets of success and replicate.
- #28 What we’ve learned is that an Ag Rollout is itself at iterative and incremental process.
- #29 This means that the testers should participate in all delivery-team planning, ceremonies, and work that is being performed by the team.Backlog grooming, iteration planning, delivering software, attendance at the standup, demos & reviews, and retrospectives should all include the QA members.In an Agile model, the testers have equal footing with the rest of the delivery team and are expected to help plan, help get upcoming stories ready for future iterations, task out stories, and to fully participate in the collaborative commitment of the delivery team.
- #34 What this really looks like is not so much steps as overlapping waves.One of the early decisions you make is about how far you want to go and how fast.how far – not all the way agile? a program?how fast – how much learning? how much appetite for change?
- #45 Create a sense of team identity by defining teams.
- #62 Compliancy is not allowed – this approach will allow you to say on the green curveIt is the path toward a maneuverable workforce –with alignment and initiative