Continuous Integration – Don’t just kick the can further down the road
20 Dec 2017
Following my previous blog on Extreme Programming, I wanted to talk about another XP practice, Continuous Integration or CI as it is popularly known. CI is one of the most valuable practises you can bring to a development team and because of that it has become almost a mainstream activity with nearly every team I meet practicing it. Or at least claiming to practice it, as there are some very common misconceptions about CI that I’d like to discuss here. In my last post, you may remember we talked about the definition of Working Software coming from XP: “Software that passes customer-defined tests in a production (or production-like) environment.” Known in Scrum as “Done”. If your work is not passing the acceptance tests you agreed with your customer in the production environment, or an environment that is as identical to the production environment as to make no difference, there is a risk that it will come back to you. In other words, if your work does not meet this criteria, it is not yet completely integrated. This brings me to a conversation, a very common conversation, that happens in pretty much every Certified Scrum Developer course I run. The conversation […]
My name is Karl Scotland and I help businesses become Learning Organisations.
Over the last 15 years I have been an advocate of Lean and Agile approaches to achieve this, working with companies including the BBC, Yahoo!, EMC Consulting and Rally Software. During this time, I have been a pioneer of using Kanban Systems for software development, a founding member of both the Lean Systems Society and Limited WIP Society, as well as being active in the community and a regular conference speaker. As a result I was awarded the honorary Brickell Key Community Contribution Award at the 2013 Lean Kanban North America conference.
To connect with Karl on social media, simply click on the Twitter and LinkedIn buttons below.