Laurent Bossavit
Sometimes it feels like a fact of life, like death and taxes, that software developers are ever cursed to write code full of bugs, then take them out one by one, with the patient assistance of testers (also known as “quality assurance”). At times we could believe that programming is special, that the Lean ideal of “right first time” cannot apply there, and developers and testers are doomed to the current uneasy (and sometimes adversarial) relationship. Here is a real story, not a fairy tale, to shine a hopeful light for those walking the Lean path...
Bernard Notarianni, Umolelo
This is the true story of a software creation team who wanted to double its productivity. See how a PDCA-like approach led them to implement the Dojo and Mob programming practices, what did work and what needed to be improved. Bernard show how the practices relate to the TWI concepts described in “Toyota Talent” and how this leads to a “Training Within Software” practice, adapted to highly creative activities performed by software creators. This session should generate new ideas for agile teams who want to improve their skills and efficiency through a standardized...
David Bogaerts, ING Bank
The ING Bank case study: In 2010 we started working Agile in our Internet Banking department (28 teams & 220 employees) and created nice results. It felt however as if we kept banging our heads against big issues all the time. Introducing technical improvements only helped to solve part of our issues, however we never seemed to get away from trouble shooting. Slowly we started to realize that if we wanted to make real progress, we had to deal with the real root cause: us as a management team. Organize ourselves as management and have the discipline of not disturbing...