Scrum/Kanban installs systems of Agile planning and gives the team control of their own processes–very important things. However transitioned teams rarely, by themselves, create engineering practices that enable delivering software monthly or weekly and usually continue doing their old development practices beneath the new Agile planning and execution framework. When looking at changing an organization, Scrum and Kanban are the outer-most layer of the onion, leaving untouched what’s supposed to be the result of all the planning work: working software.

 

An Agile framework that is focused on how software was written, eXtreme Programming, unfortunately isn’t widely adopted. Organizational change experts expected Scrum teams would eventually adopt practices like TDD and slowly adapt their way into becoming an XP like team, but for a variety of reasons which we’ll deconstruct in this series, this adoption rarely happened.

 

Next episode, we will explain how to do TDD.