The History Of Agile and Lean

This animated whistlestop tour of Agile and Lean starts in 1913 with Henry Ford's first assembley line. It then moves to Toyota and how they gave birth to the Toyota Production System (TPS). It looks at the values and principles of TPS before moving onto the practices that underpin this system. It shows how TPS went global and morphed into the Lean that we know today. And finally, we look at how Agile grew as the challenges people were facing evolved and became more complex!
To dive deeper into Agile, Scrum and more, consider exploring my comprehensive collection of books and resources designed to enhance your Agile expertise. Whether you're a general agilist, a Scrum Master or a Product Owner, these guides provide practical, actionable insights to support your professional growth:
1) Book: Practical Scrum Master Step by Step: The Perfect Guide for Scrum Master Activities (www.amazon.com...)
2) Book: Practical Scrum Master Pocket Book( www.amazon.com...)
3) Book: Practical Product Owner - Fundamentals: The Essential Manual for Product Owner Activities in Scrum ( www.amazon.com...
4) Online Scrum Master Course: Scrum 101- A fundamental look at the agile Scrum Master role (www.udemy.com/... )
5) My Website - High Performance Agile Teams: www.hptagile.com/

[@benjaminshonubi4461]

very good vid I appreciated the history lessons of where agile came from

[@camgere]

Very nice overview. There are some conflicts between agile and lean. Lean manufacturing is very big on interchangeable parts with low variability and precise specifications. Agile forgoes specifications so that it can pivot quickly and cheaply as it learns abouts its product and customer acceptance. Both believe in knowledge first, decisions second. Lean believes that you can use reductionism to break tasks into their component parts (system engineering). The interfaces are likely to change as you do detailed design. It is important to have integration events that put the pieces back together again. Agile is big on doing one piece at a time with unit testing but no integration testing (maybe an external Quality Assurance integration testing by people who do not understand the design). They trust that the interface specifications are perfect. Kind of ironic for people who don't believe in specifications.

[@motionforgecg]

Excellent vid - please do make more :)

[@Alex-qr4do]

møller er bøs