Adding Sanity To Your Agility
Embed Size (px)
Transcript of Adding Sanity To Your Agility
- 1.Adding Sanity to Your Agility Doing What Works over Doing What Youre Told
2. How do we promote agility? (agility over Agile) 3. World HeadquartersMinneapolis, MN Company motto: all hippy, all the time 4. Contextual Agility 5. DevJam Agility: Why over HowCreating Community and Common VisionForm Communities (Chartering)Composing a Product(Backlogs - Personas Story Maps)Create an Eco-System (Iteration 0 Common Workspace) Prioritizing and PlanningProduct Releases (Releases - Priorities - Estimates)Iterative Delivery (Iterations Stories/Tasks - Estimates) Iterative Delivery and TuningStaying Connected(Daily Standup Common Workspace)Tracking Progress(Task Wall - Burnchart - Velocity)Technical Agility(Continuous Integration Test Driven)Delivering Value (Acceptance Test - Story Sign Off)Tuning and ImprovingValidating Progress(Reviews Product Presentations)Reflect and Improve(Retrospective) 6. Reframing Toward SanityPreproduction ( Getting Ready to Produce ) -------------------------------------------------- Finding Your Groove( Getting Productive ) --------------------------------------------------Keeping the Band Together( Staying Productive ) 7. Pre-Production ( getting ready to produce ) 8. Pre-Production Work Assessment - Interviews Coaching Plans - Practice Selection Chartering Personas - Story Mapping Creative Eco-Systems Road Map Planning 9. Getting to Know the Band Skills + Collaboration + Vibe = Groove 10. Change Is A Process This is what you should doPrescriptive vs. Descriptive This is what I have seen workDogma Kills 11. Getting the Know the CommunityCoaches are Producers 12. Assessing Each GigDiscuss current process (how do you deliver value / software?) Get to know their perspective (motivation, constraints and knowledge) Discuss strengths and constraints (community - products - delivery - tuning) 13. Suggesting Practices Sprint BacklogBurndownSprint Reviews Sprints Product BacklogsDaily Scrum Meeting Cross Functional TeamsTest Driven Iterations Mura Muda RefactoringReleasesKanban Personas Iteration 0 VelocityKaizen User StoriesBurnup Acceptance Tests Chartering Evolutionary DesignRetrospectivesContinuous Integration Common Workspace Domain Driven Design Information Radiators Collective Ownership Sustainable Pace 14. Meaningful Groupings CharteringBurnup / Velocity Common WorkspaceAcceptance TestsInformation Radiators Test Driven / Refactoring Iteration 0Continuous IntegrationCommunity - TeamsIterative Delivery Products - PlanningTuning - Improving Product BacklogsStand Up MeetingsPersonas Product Reviews User Stories / Story MapsRetrospectives Release / Iteration Planning Continuous Feedback 15. Respectful Change Change must happen with people and not to them 16. Building a Coaching Plan What changes will help and why?(practice suggestions)How much change can they absorb? (respectful change - the right selections)How can you measure the change value? (practice tests coaching guides) 17. Finding Your Groove( getting productive ) 18. What is Thing Called Groove? Groove is that quality thatmoves the song forward _________________When a song has a good groove, it invites us into asonic world that we dont want to leave 19. Agile Groove BuildersPlanning(iteration planning)Discovery (story telling)Hang Time (stand ups)Delivery(accept tests reviews)Tuning(retrospective indicators) 20. Story Telling over Sentence Reading 21. Story Telling Variations 22. SharingCoachingStories -Teaching Through Story Telling 23. What Are Your Stories?Coaching stories? Project stories? Product stories Coding stories? Agile stories? 24. Sensing and Acting ( mining coaching indicators ) 25. Discovery Indicators 26. Connection Indicators - standing is the easy part - 27. Learning Indicators 28. What are your indicators? during planning sessions during stand up meetings during reviews and retrospectives- what tells you success is present? - 29. Keeping theBand Together ( staying productive ) 30. Sustaining AgilityEvolving Your Process Monitoring HealthEmpirical SkepticismDealing with ChangeThe Beginners Mind Staying Curious 31. Challenging, Evolving & Changing 32. Empirical Skepticism Estimation is a waste of time, why should we bother? Our stand up in boring, do we need tokeep doing it? Is our retrospective really helping us improve? 33. Beginners Mind Beware the Expert Trap 34. Undamaged By the Past - being new has its advantages - 35. Avoiding the Expert Mind Trap 36. Beware Epistemic ArroganceThe difference between what you know and what you think you know 37. How do we promote agility? (agility is a tool for the community) 38. Questions ________________________________________Coaching and Developing Agilitydavid.firstname.lastname@example.org www.devjam.com 2010 DevJam - All rights reserved.