Agile origins lightning talk - Lean Agile Edinburgh
•Download as PPTX, PDF•
0 likes•289 views
I did a short talk on the origins of agile and some of the key principles behind the manifesto. Recorded by Product Forge and available on youtube https://youtu.be/EXkjNn1R0-c
Recommended
Recommended
More Related Content
What's hot
What's hot (9)
Similar to Agile origins lightning talk - Lean Agile Edinburgh
Similar to Agile origins lightning talk - Lean Agile Edinburgh (20)
Recently uploaded
Recently uploaded (17)
Agile origins lightning talk - Lean Agile Edinburgh
- 1. Laz Allen Agile Origins and Principles
- 11. The Agile Manifesto “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:” INDIVIDUALS AND INTERACTIONS over processes and tools USEFUL WORKING SOFTWARE over comprehensive documentation CUSTOMER COLLABORATION over contract negotiation RESPONDING TO CHANGE over following a plan While there is value in the items on the right, we value the items on the left more. Ref – An ad hoc manifesto Source – AgileManifesto.org
- 14. The Agile Onion Tools Practices Principles Values More visible – less powerful Less visible – more powerful Mindset
- 15. Small self organising teams Ref: Dunbar numbers and Metcalf's law
- 17. Incremental v Iterative development Image Ref: Henrik Kniberg
- 18. Stop starting, start finishing
- 19. Making Time To Improve
- 20. Toyota Production System (TPS)
- 21. Lean beyond manufacturing Lean Startup (2011) Lean Product Development (2009) Lean UX (2013)Lean Analytics (2013) Lean Software Development (2006)
- 22. Recommended Reading Recommended Reading • Agile Manifesto • Agile Marketing Manifesto • Agile Alliance • Succeeding with Agile Blog • What Exactly is the Agile Mindset? • Scrum Guide download page • Lean from the trenches free PDF • Agile apocrypha and an ad-hoc manifesto
Editor's Notes
- TIMING GUIDELINE = 2 MINUTES The Agile manifesto was written back in early 2001 by a group of 17 people with backgrounds in different software methodologies. Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and others sympathetic to the need for an alternative to documentation driven, heavyweight software development processes convened. It is also backed up by 12 principles which can be found on the Agile manifesto website. We won’t cover these in this course but I recommend taking a look at the website and reading these.
- Liz Keogh Lyssa Adkins Sal Freudenberg Katherine Kirk Saket Bansal Mary Poppendieck Ash Maurya Top left clockwise
- TIMING GUIDELINE - 1 MINUTE Talk about the relevance of the manifesto today and that it is still very applicable, but it makes sense to replace “working software” with useful software (or useful product)
- TIMING GUIDELINE = 2 MINUTES Tools are the things we use – very overt Practise are the detailed rule sets we follow including processes and role descriptions Principles are generalized rules that we attempt to follow whenever possible Values are preferences to be applied, in a choice between x and y we prefer x (from holocracy) Mindset is baked in system 1/animal/lizard brain, it’s what you do when you do stuff without engaging conscious thought – most powerful, hardest to change
- TIMING GUIDELINE = 2 minutes
- TIMING GUIDELINE = 2 minutes
- TIMING GUIDELINE = 2 minutes
- TIMING GUIDELINE = 2 minutes
- TIMING GUIDELINE = 2 minutes
- TIMING GUIDELINE = 4 minutes TPS and Toyota (1948-75) Lean manufacturing has its origins in Toyota who developed the Toyota Production system, originally known as “just in time production” in Japan between 1948 and 75. This didn’t become known as Lean manufacturing until around the late 80s. The book “The machine that changed the world” written by Womack et Al in 1990 tells the story. The main objectives of TPS were to design out overburden (muri), inconsistency (mura) and waste (muda). There are two pillars to TPS: Just in Time (JIT) – making only what is needed, when it is needed in the amount it is needed. Jidoka – Autonomation (automation with a human touch) Principles behind TPS include continuous improvement, respect for people, long term philosophy (even at the expense of short term goals), continuously solving root causes of problems drives organisational learning, add value to your organisation by developing people and partners. The Toyota Way was published in 2001 and describes the 12 management principles in Toyota. The book talks about many companies who have tried to copy TPS but failed. It cites the main reason for failure as not having the right Lean leadership in place.
- TIMING GUIDELINE = 2 minutes Lean software development - In 2006 Mary and Tom Poppendeick published “Lean software development” and went on to publish a number of other books in this field. They took several of the principles from Lean manufacturing and applied them to software. The principles are very similar to the TPS principles and include eliminating waste, amplify learning, decide as late as possible, deliver as fast as possible, empower the team, build integrity in, see the whole.