Over the past two decades agile has solved our inability to deliver software frequently. Largely this can be attributed to AGILE PROCESS improvements, smaller tends to flow faster.
• smaller work items (user stories and features)
• smaller batch sizes (Sprint backlogs/ WIP limits)
• shorter cadence (2-4 week iterations)
ENGINEERING improvements seem less necessary & teams feel like agile process is being done TO them.
Is the ability to release frequently with existing engineering practices sufficient? Should we declare victory now?
Surely the next step is to amplify our focus on ENGINEERING? Not WHAT we build or HOW MUCH we build but HOW we actually build it. Engineering efficiency is the key to moving beyond frequent delivery, to continuous or on-demand delivery. We cannot get there without "Continuous attention to technical excellence enhances agility" and for this we need engineering teams fully engaged and on board.
XP was once our solution for "Uncovering better ways of developing software". This talk revisits XP in the context of where Agile is now and looks to rediscover XP as a pathway to increased agility.