version control systems a decade ago.
Right now some of the most popular open-source build systems (like Jenkins) have absolutely horrible user experiences. I would expect to see more iteration in the area of look and feel on these systems as people realize how critical the visibility is. This will in turn make CI much more effective for organizations that deploy it.
Noel: What's the best way for those who want to incorporate massive continuous integration into their own companies to start the process?
Jesse: You will need a fairly high degree of test automation right up front. You'll need to invest in a build system (although most engineering shops these days have one already). If you're trying to do this at scale, you're probably going to need a cloud provider or a lot of hardware lying around.
Forming a small team to pull together the different threads and build a prototype can be a great way to begin the process of building a scalable CI system.
Ultimately, keeping continuously integrated is a way to push more customer value into production. This is possible because you always know the state of your build, and you free yourself to retire technical debt, as well as keep lots of engineering teams all working on the same codebase with minimal down-time for reintegration.
If you are struggling to hit your delivery dates because you have uncertainty in the QA phase of your software development lifecycle, going with a continuously integrated system is a fantastic way to close the gap.