I don't do agile, i am agile (Barry O'Reilly)
•Download as PPTX, PDF•
1 like•643 views
1. The document discusses various agile frameworks like Scrum, XP, and Kanban and their associated practices. 2. It emphasizes that organizations should focus on using practices that suit their specific context rather than strictly adhering to a single framework. 3. The document advocates for a lean, adaptive approach to agile by continuously questioning practices, eliminating waste, and prioritizing delivering value over following prescriptive processes.
Report
Share
I don't do agile, i am agile (Barry O'Reilly)
- 1. I don’t do agile, I am agile!@BarryOReillywww.barryoreilly.comhttp://www.linkedin.com/in/barryoreilly
- 2. Whoare ThoughtWorks?Enterprise Agile and Technology consulting Offices in US, UK, Germany, India, Brazil, China and Australia1,800 people worldwideCreators of GO!, Twist and MingleMartin Fowler & Jim Highsmith
- 3. What will we cover?
- 4. Problems adopting and practicing Agile in organisations
- 5. Follow what is in the book – we’re Agile!
- 6. Agile project failing to deliver or live up to expectations
- 7. But we are doing everything X says to do
- 8. Maybe Agile isn’t for usIt does not workA myth
- 11. SCRUM - PracticesMeetingsDaily Stand UpSprint PlanningShowcaseRetrospectiveTime-boxingSprintSpikes ArtifactsProduct BacklogSprint BacklogBurn DownRolesSCRUM TeamSCRUM MasterProduct OwnerUsers
- 12. XP – PracticesFeedbackUser Stories (Planning)Whole team Test Driven DevelopmentPair ProgrammingWelfareSustainable PaceShared UnderstandingSimple DesignSystem MetaphorCollective Code OwnershipContinuous ProcessContinuous IntegrationDesign ImprovementSmall Releases
- 13. KanbanVisualise The WorkflowLimit Work In ProgressManage FlowMake Process Policies ExplicitImprove Collaboratively
- 15. Instead of trying to do everything that’s prescribedAsk why are we doing it?
- 16. Do we need to do it?Does it work for the product we trying to build?
- 17. Reverse thinking
- 18. The best place to begin an intellectual journey is at its end – Russell Ackoff
- 19. Visionaries look ahead to a desired endKnow where they want to be
- 20. Work backwards to find a way of getting there
- 21. Bad smells
- 22. To do more of what is not working now, is to do more of what will not work in the future
- 23. Trying to do the wrong thing right
- 25. How do we know?
- 27. XPLeanKanban
- 29. Amplify learning
- 30. Deliver as fast as possibleIt is important that an aim never be defined in terms of a specific activity or method. – Edward Deming
- 31. Go Compare
- 33. Specialist teams
- 35. Add Items when capacity
- 36. Estimation OptionalSCRUM14 PracticesTime boxed
- 38. Roles Prescribed
- 39. Cannot Add Items
- 43. Small releases
- 44. Planning game Prescriptive Adaptive
- 45. Focus on using the practices that suit the context Don’t simply stick with one discipline and one alone
- 46. Great idea! When do we start?
- 47. Day One to Last Day
- 48. Example
- 49. Day OneManagement felt need to control and manage teamShowed a lack of involvement in the project (Agile too time consuming)Wanted progress reports every two weeksSCRUM by the bookTime-boxing led to mini-Waterfall mentalitySprint planning meeting (taking hours and all team members)Build broken, still go to prescribed meetingsEstimate in points, task in hours, Burn down in hours
- 52. Last DayOnly formality Showcase to external stakeholdersReport outwards on velocity covered since last report cycleStakeholders require continual engagement at story review and showcaseForced to prioritisedDevelopersStory huddles meant they only review stories they work onFocus on writing code, not hang out in meetings
- 53. What are the indicators for what practices to use?
- 54. What To Think About….Project BriefGreen or Brown FieldsNew Product DevelopmentHeavy Lifting Integration
- 55. What To Think About….OrganisationExperience of AgileOpen to changeCulture People need to feel secure, otherwise display defensive behaviour
- 56. What To Think About….Hand over and collaboration Always availableNot with team continuallyIntermittentlyOnly attend schedule meetings
- 57. What To Think About….Composition Of The TeamCo-locatedDistributedSame working hoursDifferent time zones
- 58. What To Think About….EnvironmentTechnologyTools Office SpaceDesk Space
- 59. What To Think About….ReleasingAutomated or Manual How often can you deploy?On demandDaily, Weekly, MonthlyScheduled cycle
- 60. What To Think About….Feedback loopsStakeholdersCustomersUsersCannot improve if you do not get it
- 61. So back to SCRUM, XP or Kanban
- 63. Specialist teams
- 65. Add Items when capacity
- 66. Estimation OptionalSCURM14 PracticesTime boxed
- 68. Roles Prescribed
- 69. Cannot Add Items
- 73. Small releases
- 74. Planning gameStop thinking about what discipline to useStarting thinking about what practice will be useful
- 76. Specialist teams
- 78. Add Items when capacity
- 79. Estimation OptionalSCURM14 PracticesTime boxed
- 81. Roles Prescribed
- 82. Cannot Add Items
- 86. Small releases
- 89. Roles Prescribed
- 90. Cannot Add Items
- 92. Event Driven
- 93. Specialist teams
- 95. Add Items when capacity
- 97. Iterative
- 100. Small releases
- 102. There is nothing so useless as doing efficiently that which should not be done at all - Peter Drucker
- 103. Minimum amount to succeed
- 104. MudaEliminate waste Not helping get rid of itUsing more tools, people or equipment than is neededSoftware Development is a value creation processPerfect process has no unneeded waste
- 105. Delivering as fast as possibleEnd goal is to deliver a productSooner the product is deliveredSooner you get feedbackSooner you can improve it
- 106. Amplified learningContinuous learning processMaking mistakes and learningIncreased feedback
- 107. Question Everything
- 108. Is what we are doing valuable or slowing us down?
- 109. Is it relevant for what we are trying to do?
- 110. What purpose is it meant to serve- is it achieving it?
- 111. If we didn’t do it what would happen?
- 113. Team arrives at maturity when it invests more in strategies and tactics that do not work more than ones that do
- 114. Learn more when things are wrong not right
- 115. Try things outDon’t be afraid to fail
- 116. Do not waste your failures
- 117. It's not FAILURE that we should celebrate - but the LEARNING that ensues
- 118. Kaizen
- 119. Thank youIf you like what you saw talk to me about joining ThoughtWorks