Integration Hell | Glossary

Definition

Integration Hell is one of the biggest challenges in traditional software development environments. The Integration process is very rarely smooth and seamless, and results in hours of re-fixing the code, sometimes leading up to days, before it can finally integrate. One of the biggest challenges being the dependency relationship between the code that’s built, and the rest of the code in the system.

Continuous Integration is the process defined to completely avoid this process, by creating an infrastructure where the built-in code can be integrated immediately into the project. It overall goes to great lengths to encourage team members to integrate regularly.

Further Reading

  •  “Continuous Integration: Improving Software Quality and Reducing Risk”(book), by  Andrew Glover, Paul M. Duvall, and Steve Matyas.

Integration | Glossary

Definition

Agile integration, as a software development practice favours continuous code releases in shorter bursts, over longer, prescribed cycles. This is done to reduce instability, complexity and risk during a software release. It’s a methodology that employs strict automation, version control and rapid problem resolution in order to ensure the availability of stable updates at any given moment.

Further Reading

  • “Cost Estimation in Agile Software Development: Utilizing Functional Size Measurement Methods”(book), by Stefan Luckhaus