Being agile about agile


Published on

A real world overview of Agile methodologies

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Being agile about agile

  1. 1. Being Agile With Agile For Lovely People at Bethnal Green Ventures Project Andiamo
  2. 2. We’ll Cover • Quick history • What is Agile in the real world • Two methodologies called Scrum and Kanban Project Andiamo
  3. 3. Disclaimer Project Andiamo This is what I’ve learnt not textbook says I swear a lot
  4. 4. A Brief History Project Andiamo On February 11-13, 2001, mountains of Utah, seventeen people met to talk, ski,. What emerged was the Agile Software Development Manifesto. Representatives from Extreme Programming, ! Now, a bigger gathering of organizational anarchists. ! The only concern with the term agile came from Martin Fowler most Americans didn’t know how to pronounce the word agile.
  5. 5. Project Andiamo
  6. 6. 12 Principles of Agile • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Project Andiamo
  7. 7. Adaptive Vs Predictive Project Andiamo
  8. 8. Shit happens so stop pretending Project Andiamo
  9. 9. That doesn’t mean you don’t plan Project Andiamo
  10. 10. You plan around being wrong Project Andiamo
  11. 11. If you’re building something new you’re free climbing Project Andiamo We had to persuade the business that they didn’t know where they were going they just broadly knew the destination
  12. 12. Types of Agile • Adaptive Software Development (ASD) • Agile Unified Process (AUP) • Crystal Methods (Crystal Clear) • Dynamic Systems Development Method (DSDM) • Extreme Programming (XP) • Feature Driven Development (FDD) • Kanban • Lean software development • Scrum • Scrum-ban Project Andiamo
  13. 13. Scrum "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" as opposed to a "traditional, sequential approach". Project Andiamo
  14. 14. Scrum Project Andiamo
  15. 15. Project Andiamo
  16. 16. Project Andiamo
  17. 17. Retrospective Project Andiamo
  18. 18. Story Points Project Andiamo
  19. 19. When is it good? • Your team works together in the same place at the same time • Multiple development teams • Defined roles • You need discipline • Corporates/Customers: It feels more processey Project Andiamo
  20. 20. Kanban Project Andiamo Toyota Just in time manufacturing
  21. 21. Project Andiamo Kaizen - Improvement or Change for the best Genchi Genbutsu - go and see
  22. 22. Project Andiamo Kaizen - Improvement or Change for the best Genchi Genbutsu - go and see
  23. 23. Project Andiamo Kaizen - Improvement or Change for the best Genchi Genbutsu - go and see
  24. 24. Project Andiamo
  25. 25. Project Andiamo Principles 1. Visualise 2. Cards 3. WIP limit
  26. 26. Project Andiamo Difference between done and successful
  27. 27. Project Andiamo Principles 1. Visualise 2. Cards 3. WIP limit
  28. 28. Push Vs Pull Project Andiamo We agreed to be available together 1 entire day each week Blockage meetings
  29. 29. SCRUM Project Andiamo
  30. 30. Kanban Project Andiamo
  31. 31. When is it good? • Your team is in different places and works at different times • Experienced and confident team • No politics Project Andiamo You can lay Kanban over the top of SCRUM Kanban itself is not a software development process
  32. 32. Project Andiamo Story points Velocity Burndown People Hours
  33. 33. Principles I’ve Learnt • Users first • Use cases are mandatory • We aim to fail fast • We will make mistakes, we accept this and mitigate losses up front • Everything we build is • Quickly iterative • Disposable • Doesn't constrain future growth • Agnostic • We always test (e.g. TDD, BDD) but real world tests are more important • The value in the future is context. How we get insights, make better decisions, and tell stories with that data Project Andiamo
  34. 34. One Question Project Andiamo
  35. 35. What is the fastest, cheapest, and best way to screw this up? Project Andiamo All these things are just tools they won’t stop you screwing stuff up
  36. 36. Now iterate Project Andiamo