The Ultimate Agile Mix Tape (Agile 2017)
Download as PPTX, PDF2 likes718 views
The document discusses the diverse interpretations and applications of 'agile' methodologies, emphasizing the importance of principles and practices in delivering valuable products efficiently. It contrasts popular agile approaches such as Scrum, XP, Kanban, and Lean, explaining their unique focus and contribution to continuous improvement and workflow optimization. The author encourages teams to adapt and evolve their processes for enhanced performance while addressing potential points of friction in implementing these agile methods.
The Ultimate Agile Mix Tape (Agile 2017)
- 1. The Ultimate Agile Mix Tape
- 2. Goal “Walk away with some ideas of how to use the principles and practices from the various Agile approaches to help you develop valuable products in the best way possible for you.”
- 3. Reaching that goal… Level set on the term ‘agile’ Flavors of ‘agile’ Effective combinations Points of friction
- 4. Tommy Norman
- 5. Tommy Norman Agile Nashville User Group www.agilenashville.com
- 6. Tommy Norman Music City Agile www.musiccityagile.org
- 9. A little about you… Scrum XP Kanban Lean Something else?
- 10. Level set on the term ‘agile’
- 11. What does ‘agile’ mean to you? You keep using that word. I do not think it means what you think it means.
- 12. What does ‘agile’ mean to your company? You heard we’re going Agile, right? Great! More done with less people in half the time! I’ll start shopping for my second private jet now!
- 13. Concept to Cash Deliver value to our customers quickly Maximize learning and incorporate feedback
- 14. Agile is not the thing. Agile is a thing that helps you get to the thing.
- 15. Scrum doesn’t do anything… “In the end it doesn’t matter what names you use for your processes… …scrum offers individuals and organizations the opportunity to continuously improve the way they work.” - Tobias Mayer Image used without permission. Shhh! Don’t tell Tobias!
- 16. Agile doesn’t do anything… “Agile won’t fix your problems. It will tell you how screwed you are a lot earlier.” - Me
- 17. Concept to Cash
- 18. Big “Agile” little “agile” what begins with “agile”?
- 22. Scrum Fairly prescriptive/defined process Focus on project management Time-boxed Sprints for delivery User proxy via Product Owner Scrum Master to steward the process
- 24. Extreme Programming (XP) Similar process to Scrum Focus on engineering practices Time-boxed iterations for delivery Encourages direct involvement of user
- 26. Kanban Applies to an existing process Focus on work visualization Focus on maximining process flow Subset of larger Lean concepts
- 29. Lean Roots in manufacturing Focus on reducing waste Focus on people who do the work Focus on continuous improvement No prescribed/defined process
- 34. Scrum & XP
- 35. Scrum & XP User Stories Release/Iteration Planning Iterations Customer Approval Small Releases
- 36. Scrum without XP
- 37. Scrum & XP
- 38. Scrum & XP https://explore.versionone.com/state-of-agile Probably a lot more XP practices going on here Anyone actually doing just XP?
- 40. Core Principles of Kanban Visualize the workflow Make process policies explicit Measure and manage flow Limit work in progress Continuous improvement
- 41. Visualize the workflow Sprint Items To Do In Progress Done Task Task Task Task Task Task TaskTask Task Task Task Task User Story User Story User Story Unit of EffortUnit of Value
- 42. Visualize the workflow Added to Backlog Coded Tested User Acceptance Tested Deployed to Production
- 43. Visualize the workflow Sprint Items To Do In Progress Done UAT QA Test Write Code UAT Write Code QA Test User Story User Story User Story Parts of our process are represented by the tasks themselves. Some parts of the process are assumed and not represented at all. UAT QA Test Write Code
- 44. Visualize the workflow User Story User Story The board itself reflects the workflow. Much easier to see when value is delivered.
- 45. What about the tasks? User Story User Story 1. Do this 2. Do this 3. Do this 4. Do this 5. Do this
- 47. Make process policies explicit User Story • Do this • Do this • Do this “You forgot to do XYZ!”
- 48. Measure and manage flow User Story Flow
- 49. Measure and manage flow Cycle Time Lead Time
- 50. Measure and manage flow Cycle Time10 days 2 days 6 days 2 days “Why is this taking so much longer?”
- 51. Making idle work visible 2 days 4 days 2 days .5 day .5 day 1 day “Why is completed dev working sitting here idle?”
- 52. Measure and manage flow User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story
- 53. Limit work in progress User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story Flow
- 54. Flow inside the Sprint Sprint User Story A Code Test Deploy User Story B Code Test Deploy User Story C Code Test Deploy
- 55. Flow inside the Sprint Sprint User Story A Code Test Deploy User Story B Code Test Deploy User Story C Code Test Deploy
- 58. Scrumban? XP Still using a time boxed Sprint for a delivery cadence.
- 59. Scrum & Kanban More granular visualization More focus on managing flow Limiting work in progress Better metrics around flow Data driven continuous improvement
- 60. Scrumban What happens when we stop time boxing and go to continuous flow process?
- 63. Lean Principles Respect for people Optimize the whole Take an economic view
- 64. Respect for People XP People are the gooey center of your process.
- 66. Respect for People “Individuals and interactions over processes and tools.” - Agile Manifesto
- 67. Respect for People “A bad process will beat a good person every time.” - Edwards Deming
- 70. Optimize the whole Bunch of stuff happens here… Bunch of stuff happens here… Flow
- 74. Take an economic view
- 75. Take an economic view
- 76. Scrum + XP + Kanban + Lean Agile/Lean Principles Scrum XP Kanban
- 78. Points of friction What happens when we stop time boxing and go to continuous flow process?
- 79. Continuous flow process XP Let’s get rid of the Sprint entirely.
- 80. Continuous flow process Continuous FlowKanban
- 81. Continuous flow process “The Kanban Method does not ask you to change your process. It is based on the concept that you evolve your current process.” - David Anderson
- 82. Why get rid of Sprints? Release faster!
- 83. Evolving to continuous flow Scrum Get good at managing work in small, focused batches. XP Get good at delivering high quality code quickly. Kanban Get good at measuring and managing flow of work. Lean Get good at optimizing your entire system and your people.
- 84. What do we lose? Sprint User Story A Code Test Deploy User Story B Code Test Deploy User Story C Code Test Deploy 5 5 5 Velocity = 15 Cycle Time
- 85. What do we lose? Sprint Sprint Planning Review Retro Grooming Grooming Flow
- 86. Other friction points I did this yesterday. I am doing this today. No impediments.
- 87. Other friction points User Story User Story User Story User Story User Story User Story User Story User Story User Story Walk the board from right to left What can we do as a team today to move this closer to done? That’s not how my CST told me to do it!
- 88. Other friction pointsUm. If we are not doing Scrum anymore, do I still have a job? Optimize the team Servant leader Process coach
- 89. Wrap it up Frequently inspect how well your practices are helping you reach your goals and change them as needed based on your principles.
- 90. Questions?
- 91. Thank you! .
Editor's Notes
- #28: Jidoka – stop the line Heijunka – leveling, meet demand by reducing waste Kaizen – continuous improvement Takt time - the rate at which a finished product needs to be completed in order to meet customer demand.
- #41: Any see what is wrong with my list? It is not in the normal order (for a reason!)
- #42: Typical scrum board Does not really map to the underlying process, it is hidden in the task cards partially Focuses more on the flow of units of work than units of value (the top of the lean house)
- #44: Typical scrum board Does not really map to the underlying process, it is hidden in the task cards partially Focuses more on the flow of units of work than units of value (the top of the lean house)
- #48: Like definition of done in scrum, but specific for each step of the process
- #54: Limiting WIP does not require any new process/people/software/etc. You simply just have to agree to start it.
- #86: Story of leankit