Continuous Integration for Agile Project Managers: Part III (#3 in the series Continuous Integration for Agile Project Managers)
By Adam Leggett
In part 1 of this series, I hopefully provided you with an introduction to Continuous Integration (CI) and an overview of the building blocks of the CI process.
With part two, we introduced the concept of a CI life-cycle and how to bind software quality checks to discrete life-cycle ‘phases’.
In this final part, I’ll attempt to explain how you can use CI to run functional tests early in your development process and show how this helps us to promote a software release on its journey from development to production. I’ll then try to condense the three parts of this series into a handy diagram.
Automation, Automation, Automation
It should hopefully be clear by now that a successful CI implementation is largely dependent upon other processes that can be automated. Read the Complete Article
Continuous Integration for Agile Project Managers: Part II (#2 in the series Continuous Integration for Agile Project Managers)
By Adam Leggett
In part 1 of this series, I described the essential elements of Continuous Integration within the context of agile development and briefly discussed the software options for a CI server. I explained that the building blocks of CI are a version control system and a build management tool. The former creates the foundation, by giving the CI process access to the latest copy of project source code. The latter then takes the source code and, in most scenarios, transforms it into the deployable binary artefact that represents the software application being developed.
It is useful to consider this transformational process as a series of steps or life-cycle phases. By analyzing our build in this conceptual way, we can better understand how to ‘bind’ or attach actions to each distinct life-cycle phase. Read the Complete Article
Continuous Integration for Agile Project Managers: An Introduction (#1 in the series Continuous Integration for Agile Project Managers)
By Adam Leggett
Any Agile Project Manager worth his salt should be aware of the term ‘Continuous Integration’ (often shortened to ‘CI’). But what is it, how is it done and why should you care?
This series of articles aims to answer these questions, so you can start your next project, or re-configure an existing project, armed with the necessary understanding about this key practice within agile software delivery.
The basic premise of CI is pretty straightforward. An agile team needs a repeatable and reliable method to create a build of the software under development. Why so? Well, if its not already obvious, you may want to revisit the principles behind the Agile Manifesto. Within them you will notice a number of references to ‘working software’, and the foundation of any working software is a stable, tested build. Read the Complete Article
PM Hut currently has 570 contributors! Please contact us in case you’re interested in publishing your Project Management articles on PM Hut and joining the list below!
An article published on PM Hut may be eligible for PMI PDU credits under the Category D of the CCR Program (Giving Back to the Profession). This category is capped to 45 PDUs per 3 years. Authors claiming their PM Hut published articles for PMI PDUs are required (by PMI) to supply PM Hut’s physical address in their application. Please contact us for this information.
Please note that it is the responsibility of the author to handle the whole process for claiming the PDUs, PM Hut’s role is currently only limited to supplying its own physical address to the author.
Read the Complete Article