Continuous Integration is by itself already a practice. It is one of the most critical to adopt to enable the fast flow of work through the value stream. However, many teams believe Continuous Integration is just a tooling problem, to then say they practice Continuous Integration.
Though they often do not and hence miss out on the benefits that come along with it. This session goes deeper into the practices that each on their own enables Continuous Integration. Learn how to gain fast feedback, increased stability and higher throughput!
Key takeaways:
- Be able to define what a state of Continuous Integration is
- Be able to enumerate the practices required to achieve Continuous Integration
- Be able to understand the practices
References:
- The Article Series: The Practices That Make Continuous Integration
- Continuous Integration Certification, Martin Fowler
- Software Configuration Management Patterns, Steve Berczuk with Brad Appleton
- Continuous Integration, Paul Duval, Steve Matyas, Andrew Glover
- The Art of Agile Development, James Shore, Shane Warden
- On DVCS, Continuous Integration and Feature Branches, Jez Humble
- Make Large Scale Changes using Branch-by-Abstraction, Jez Humble
- Parallel Change, Danilo Sato
- Introducing Branch By Abstraction, Paul Hammant
- Branch by Abstraction, Paul Hammant
- Feature Toggles, Pete Hodgson
- The $440 Million Software Error at Knight Capital, Henrico Dolfing
- Acceptance Testing for Continuous Delivery, Dave Farley
- Continuous Integration on a Dollar a Day, James Shore
- Tools versus Practices – lessons from DIY
- Toyota Kata, Mike Rother
- The Role of Continuous Delivery in IT and Organisational Performance, Dr. Nicole Forsgren, Jez Humble