Thursday, January 10, 2013

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.

2 comments:

BBG said...

This is a really good technique for communicating techy stuff to business users.

Anonymous said...

Undeniably consider that that you stated. Your favourite reason appeared to be on the net the simplest factor to take into
accout of. I say to you, I definitely get annoyed at the same time as other people think
about concerns that they plainly don't understand about. You managed to hit the nail upon the highest and also outlined out the entire thing without having side effect , other people could take a signal. Will probably be again to get more. Thank you

Also visit my web page ... email newsletter templates