principle-centered agility - your path to better options
DESCRIPTION
Do you want to have a high functioning Agile team? If so, this session is for you! We’re going beyond the rules of agile frameworks and learning to apply those principles to improve our teams and companies! The 12 principles of the Agile Manifesto capture the reasons we are able to deliver better software. This is the “why” for some of the rules behind Scrum and Kanban. The principles ought guide our decisions about practices, scaling, and solving tricky problems! In this presentation we will use the 12 Principles of the Agile Manifesto as our foundation. Then, we will apply techniques such as Force Field Analysis to apply the principles to your challenges at work. Lastly, we will use principles of change management to make the change more likely to stick. The outline for the presentation is: Explore the principles; which ones are present or absent in your environment? Introduce Force Field Analysis Use Force Field Analysis to explore what drives a specific behavior Use the Agile Principles to generate new options for tackling your team’s challenges Explore effective change management techniques With these five activities, you will leave with a framework for change to apply when you return to work and continue on your agile journey.TRANSCRIPT
- 1. Principle-Centered AgilityYour Path to Better Options
2. 1. Explore the principles2. Introduce Force Field Analysis3. Use Force Field Analysis4. Generate New Options5. Explore Change ManagementWorkshop Goals2 3. WHAT IS AGILE?3 4. We are uncovering better ways of developing software bydoing it and helping others do it. Through this work wehave come to value:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planThat is, while there is value in the items on the right, wevalue the items on the left more.Manifesto for AgileSoftware Development4 2001, the authors 5. EXPLORE THE 12 PRINCIPLES5 6. Sometimes its present, sometimes its not.Explore the 12 Principles6Its pretty natural here.This is challenging here. 7. Deliver working software frequently, from acouple of weeks to a couple of months, with apreference to the shorter timescale.Principle 3Source: www.agilemanifesto.org7Risk Risk RiskProjectStartsRisk 8. Principle 78Working Software is the primary measure ofprogress.Source: www.agilemanifesto.org 9. Continuous attention to technical excellenceand good design enhances agilityPrinciple 9Source: www.agilemanifesto.org9 10. Business people and developers must worktogether daily throughout the project.Principle 4Source: www.agilemanifesto.org10 11. The most efficient and effective method ofconveying information to and within adevelopment team is face-to-face conversation.Principle 6Source: www.agilemanifesto.org11 12. 12Face-to-face is the most effective - Try VideoAlistair Cockburn 2009Richness of communication channelCommunication Effectiveness2 peopleon phone2 peopleon chat2 people atwhiteboard(Courtesy of Thoughtworks, inc.)PaperVideotape 13. Mural.ly13 14. Principle 214Photo By Nilfanion (Own work) 15. Principle 215Welcome changingrequirements, evenlate indevelopment. Agileprocesses harnesschange for thecustomer'scompetitiveadvantage.Source: www.agilemanifesto.org"Emirates Team New Zealand at the Louis Vuitton Cup 2013"by Frank Schulenburg 16. Simplicity--the art of maximizing the amountof work not done--is essential.Principle 10Source: www.agilemanifesto.org16 17. The best architectures, requirements, anddesigns emerge from self-organizing teams.Principle 11Source: www.agilemanifesto.org17 18. Build projects around motivated individuals.Give them the environment and support theyneed, and trust them to get the job done.Principle 5Source: www.agilemanifesto.org18 19. Agile processes promote sustainabledevelopment. The sponsors, developers, andusers should be able to maintain a constant paceindefinitely. Source: www.agilemanifesto.orgPrinciple 819Proximity to deadlineEffort 20. At regular intervals, the team reflects on howto become more effective, then tunes and adjustsits behavior accordingly.Principle 12Source: www.agilemanifesto.org20 21. Principle 121Our highest priority is to satisfy the customerthrough early and continuous deliverySource: www.agilemanifesto.orgof valuable software. 22. Reflections22 23. FORCE FIELD ANALYSIS23 24. 24 25. APPLY25 Use +/-/? Analysis as Input Brainstorm a change Identify Driving/Restraining Forces Weight the Forces Share with a Partner 26. Reflections 27. GENERATE OPTIONS27 28. Reflections 29. Generate Options29Desire: Get Software to our CustomersFactor Selected: Defect-averseAgile Principle New Option10: Simplicity--the art ofmaximizing the amountof work not done--is essential.Ruthlessly cut scope on remainingstories to get a TRULY minimalviable product. (i.e. build less thatcould have defects)9: Continuous attention to technicalexcellenceand good design enhances agility.A/B TestingFlags to Turn Features On/OffRelease to a Subset of Customers 30. Reference the Force Field Analysis from earlier Select a Driving or Constraining Force Refer to the Agile Principles Identify ways to Strengthen Driving Forces Lessen Constraining forces Share with a PartnerAPPLY30 31. Reflections31 32. CHANGE MANAGEMENT32 33. Elements of Change33 34. Bright Spots Critical Moves Point to the DestinationDirect the RiderConcepts from the book Switchby Chip & Dan Heath10/19/2014 34 35. Find the Feeling Shrink the Change Grow your PeopleConcepts from the book Switchby Chip & Dan HeathMotivate the Elephant35 36. Tweak the Environment Build Habits Rally the HerdShape the PathConcepts from the book Switchby Chip & Dan Heath36 37. Direct the Rider Motivate theElephantShape thePathBright Spots Find the Feeling Tweak theEnvironmentCritical Moves Shrink the Change Build the HabitsPoint to theDestinationGrow your People Rally the Herd37 38. APPLY38 Reference the output from the last activity Pick a New Option Use the 9 change approaches to identify sometactics Share with a partner 39. Summary391. Explored the principles2. Introduced Force Field Analysis3. Used Force Field Analysis4. Generated New Options5. Explore Change Management 40. Dan NeumannE-mail [email protected] 574-514-3285Twitter @dan_sbWeb neumanagementllc.comBlog neumanagementllc.com/blog/LinkedIn www.linkedin.com/in/meetdanneumann 2014 Dan Neumann