It happened to me several times to participate in discussions regarding the implementation of the Continuous Integration [CI] practice. This is typically a task that sooner or later will be addressed by teams and organizations that are making their first steps in the world of agile software development. That are or are not aware of it.
Being able to do CI is itself a symptom and cause of being agile, at least at the level of software production. It may not be enough and anyone who has experienced a period of transition in which the development team has tried to adopt lightweight and more efficient processes, or just more customer-oriented, sooner or later he realized that a certain way of thinking and working should be extended to other departments. Indeed, it must be extended if you want to achieve sustainable development through agile methods and get all the competitive advantages that this entails, before they are basic standards that every software company will have to keep in mind. Continue reading “What is Continuous Integration about … and what is not…”