- Get best practices for transitioning to Continuous Integration
- Understand the strong link between CI and one-piece-flow, unit tests, short iterations, whole teams, refactoring, user stories, shared code ownership, distributed agile and large scale agile
Damon Poole, founder and CTO of AccuRev, a leading provider of agile development tools. Damon has over 18 years of software development methodology and process improvement experience, from small collocated teams to 10,000-person shops doing global development. He writes frequently on the topic of Agile development and works closely with AccuRev customers developing and implementing state of the art Agile techniques which scale smoothly to large distributed teams. Read Damon’s Agile Development blog.
Healthy, successful agile teams rely on a robust Continuous Integration implementation as the hub of their agile infrastructure. Many of the agile practices depend on Continuous Integration (CI) in order to provide their full value. For instance, unit tests are the most valuable when all unit tests are run automatically on a frequent basis. Scaling agile to large and/or distributed teams also depends on CI. Conversely, CI can be used as a leading indicator of the health of your agile teams.
