Continuous Integration and Automation
When one of my former teams first started implementing a few of the agile practices, the team leader learned about continuous integration and asked me to support its adoption. In our case, adopting continuous integration required moving to a new source code management tool, a new build tool, and a continuous integration server. It sounded great, but the team got tremendous resistance from the build team because the build team would have to support new tools and it was already stretched thin. Furthermore, new tools meant more costs to the company—so the uphill battle was significant.
My team solved both problems by developing the system using free, open-source software, and some of its existing hardware. It ...
Get Being Agile: Eleven Breakthrough Techniques to Keep You from “Waterfalling Backward” now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
