Listen, interview and find out what works.Not everything is broken.
Find the pockets of success and replicate.
What we’ve learned is that an Ag Rollout is itself at iterative and incremental process.
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.
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?
Create a sense of team identity by defining teams.
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
1. 3 Steps to Leading aSuccessful Agile Rollout<br />
29. Sample Iteration Planning Agenda<br />Product Vision and Roadmap [Product Owner]<br />Development status, state of our architecture, results of previous iterations [Team members] <br />Iteration name and theme [ScrumMaster]<br />Velocity in previous iteration(s) [ScrumMaster]<br />Iteration timebox (dates, working days) [ScrumMaster] <br />Team capacity (availability) [Team members]<br />Issues and concerns? [ScrumMaster]<br />Review and update definition of Done [Team Members]<br />Stories/items from the backlog to consider [Product Owner]<br />Tasking out [Agile Team]<br />Issues, Dependencies & Assumptions [ScrumMaster]<br />Commit! [Agile Team]<br />
30. Use concrete examples<br />http://www.flickr.com/photos/andywilkes/3385237379<br />
31. Point totheDestination<br />http://www.flickr.com/photos/inkybob/122476158<br />
33. Agile Rollout for 500<br />33<br />
34. Metrics aren’t the destination<br />
35. Direct the Rider<br />Motivate the Elephant<br />Shape the Path<br />
36. Find theFeeling<br />
37. No more death marches<br />http://www.flickr.com/photos/elcapitan/2387917709<br />
38. Testimonials<br />
39. Shrink the Change<br />http://www.flickr.com/photos/bernatcg/1364517772/<br />
61. How to be an Expert<br />Expert –<br />Always <br />In Flow<br />“I will keep pushing myself<br />There is always a better way”<br />Expert<br />Kick-Ass<br />Threshold<br />Ability<br />Amateur<br />“Now that I can do this,<br />I will just keep doing it this way”<br />Sucks<br />Threshold<br />Drop-out<br />Struggling/<br />Frustrated<br />“I suck at this<br />I give up!”<br />Time<br />First <br />Time<br />Years/ <br />Decades<br />Kathy Sierra – “Creating Passionate Users”<br />