SlideShare a Scribd company logo

Origins & Overview of Lean and Agile

•
•
Georg Fasching
Georg Fasching

An illustration-filled deck of slides, light on text, to aid a talk about the origin & overview of Agile & Lean in new product development, including comparison between waterfall and iterative empirical process, and also offering room to caution about the important differences between lean manufacturing and lean product development.

1 of 23
Download to read offline
Agile & Lean - Origin & Overview Agile Drops, Episode 1, Mark IV Georg(e) Fasching - @geofas
This is me. Converted to Agile Product Management from 10 years of traditional Product Management Learning, practicing, coaching, and teaching Agile since 2010 Here are some badges I collected on my journey so far:
1914 1930s
50 years later …
Origins & Overview of Lean and Agile
‘Lean’ Studies in automotive by Womack & Jones, plus Roos Books in early 90s
Lean roughly is … Maximise customer value Minimise waste
Lean really is … Respect People Continuous Improvement
Sequential ‘Waterfall’ Model ‘Waterfall’ term coined by Winston Royce’s model in 1970. “I believe in this concept, but the implementation described above is risky and invites failure.” http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf
Complexity and Creativity in Organizations Ralph Stacey, 1996
Takeuchi & Nonaka inspire revolution in software development http://mis.postech.ac.kr/class/MEIE780_AdvMIS/ paper/part3/32_The%20new%20product %20development%20game.pdf
Empirical Process Control
Options Sequential prescriptive process Iterative empirical process
Better tool for the job? Farming Software development
©2001 XP Scrum TDD
Principles behind the Agile Manifesto 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals.  Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress.  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity--the art of maximizing the amount of work not done--is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
It’s all Gelato, with different flavours.
Scrum
Extreme Programming
Kanban
LeSS - Large Scale Scrum
Scaled Agile Framework
Send any questions to: @geofas Connect at: http://linkedin.com/in/geofas/ Thanks!! Fancy a read? Public reading list at: http://geofas.com/library

More Related Content

Origins & Overview of Lean and Agile

  • 1. Agile & Lean - Origin & Overview Agile Drops, Episode 1, Mark IV Georg(e) Fasching - @geofas
  • 2. This is me. Converted to Agile Product Management from 10 years of traditional Product Management Learning, practicing, coaching, and teaching Agile since 2010 Here are some badges I collected on my journey so far:
  • 6. ‘Lean’ Studies in automotive by Womack & Jones, plus Roos Books in early 90s
  • 7. Lean roughly is … Maximise customer value Minimise waste
  • 8. Lean really is … Respect People Continuous Improvement
  • 9. Sequential ‘Waterfall’ Model ‘Waterfall’ term coined by Winston Royce’s model in 1970. “I believe in this concept, but the implementation described above is risky and invites failure.” http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf
  • 10. Complexity and Creativity in Organizations Ralph Stacey, 1996
  • 11. Takeuchi & Nonaka inspire revolution in software development http://mis.postech.ac.kr/class/MEIE780_AdvMIS/ paper/part3/32_The%20new%20product %20development%20game.pdf
  • 13. Options Sequential prescriptive process Iterative empirical process
  • 14. Better tool for the job? Farming Software development
  • 16. Principles behind the Agile Manifesto 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals.  Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress.  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity--the art of maximizing the amount of work not done--is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  • 17. It’s all Gelato, with different flavours.
  • 18. Scrum
  • 21. LeSS - Large Scale Scrum
  • 23. Send any questions to: @geofas Connect at: http://linkedin.com/in/geofas/ Thanks!! Fancy a read? Public reading list at: http://geofas.com/library