Agile Roots: Use JIT to Go Faster
Agile borrowed from the JIT manufacturing processes originally at Toyota. The Agile Manifesto itself summarized the key aspects brought into programming from JIT.
Original Agile processes like eXtreme Programming (XP) brought breathtaking speed of delivery to a waterfall world. But Agile has not stood still. From XP’s original (and aggressive) 23 week iterations, we now see individual programmers pushing new functionality to live systems several times a day!
Acceleration drives changes to an organization’s processes and skills, just as the original shift to Agile from waterfall. Organizations reluctant to address such changes, however, inhibit the acceleration. Indeed, their attempts to accelerate often result in lower morale and flawed delivery; these failures drive conservative (and destructive) attitudes against change.
In this talk, we will address a myriad of drivers for faster delivery:
- Available technologies, including Cloud, languages, and new frameworks
- Shift toward active monitoring rather than onetime acceptance testing
- Refined, lighter processes consistent with shorter cycles
- Architecture that is fault-tolerant rather than provably perfect
- Shift toward trying ideas rather than firm requirements
- Reduction in role specialists
- Reduction in delivery team size
For each of these drivers, we will describe teams that have taken these steps and the corresponding accelerated delivery.