Please log in to watch this conference skillscast.

Manufacturing companies like Toyota have realized the key to a successful organization was in defining work, eliminating waste, and producing just what's needed, when it's needed...

The various Agile methodologies get us closer to these business goals by driving out impediments and working in small batches, but what happens after we're executing and we start worrying about prioritization? Inexorably we're lead to seemingly radical new ideas like systems thinking, single piece flow, pull, and release-per-feature.

In this new paradigm, the things that used to work for us – release planning, continuous integration, TDD, evolutionary design, etc. – require tweaking or, in certain cases, out-and-out innovation.

David explains to his audience release planning, continuous integration, TDD, evolutionary design, etc. – require tweaking or, in certain cases, out-and-out innovation. And he identified the architect as a key player in the realm of Lean software development.

The tutorial continued with David grouping the audience in to practical work groups, these groups worked together to solve various case studies.

YOU MAY ALSO LIKE:

• Rules for Software Radicals (SkillsCast recorded in March 2011)
• Safe and Reproducible Deployments with Immutable Infrastructure (SkillsCast recorded in May 2020)
• Maximising 10 Percent Time (SkillsCast recorded in October 2019)