/ #Agile 

Continuous Integration vs Code Modularisation

I was writing out some conditions of satisfaction today and was about to write one about code modularisation. Some rubbish like

As a developer, I want to be able to independently release my code so that I can fulfill my obligations…..

As an Agilist, the ‘As a developer’ bit immediately rang an alarm bell, so I decided to recast this with the dicipline of thinking about real users.. do they care.. this is what I came up with.

As a business owner, I expect that different teams with different schedules and deliverables, can produce and release software independently so that each team can deliver value as soon as possible.

My first thought was that this was a 1:1 translation of the code modularisation argument but then I got to thinking about continuous integration. If you are doing CI properly then surely this real condition is fulfilled. You could in theory have multiple teams working on the most interrelated rabbit warren like codebase in the world but still manage to release small incremental changes independently. +1 for agile discipline.


Michael Dausmann

Full stack developer. Agile, Data science and Machine Learning. Love learning, speaking and dad jokes. Tweets are my own.