26 Dec '15, 7am
Two Hours Per Team and the 3 Stages of #Agile Coaching by @tastapod
For instance every team should have their code in a source control system, be writing tests and have CI, there is simply no excuse not to. But what if the technology stack you are working is hostile to these? One team I coach uses a legacy business flow modelling tool, which you “programme” by dragging icons around in a GUI. Testing is mostly manual and it doesn’t have a concept of versioning as such. I expect it is possible to freeze or snapshot its state, but not in any meaningful way, and anyway the opportunity cost means it isn’t worth it. There are other more useful things they can be doing, and this application is reasonably stable. They are gradually moving responsibilities away from it until eventually they will be able to retire it, so it makes more sense in the meantime to just live with the risk of not having that backstop of versioning and CI. So even something...