Which software development methodology is often complemented by continuous integration?

The Agile methodology is often complemented by continuous integration because it emphasizes iterative development, with frequent and incremental updates to software. Continuous integration is a practice where developers regularly merge their code changes into a central repository, where automated builds and tests are run to ensure that the codebase remains stable and functional.

In Agile development environments, teams frequently deliver working software, which aligns perfectly with the principles of continuous integration. The iterative nature of Agile allows for rapid feedback and improvement cycles, and continuous integration supports this by enabling developers to detect issues early, ensuring that new features or changes do not disrupt existing functionality.

The other methodologies mentioned do not inherently support or emphasize continuous integration. For instance, the Waterfall methodology follows a linear and sequential approach, making integration more challenging and typically occurring at the end of the development cycle, rather than continuously throughout. Documentation-driven development primarily focuses on extensive documentation, which can hinder the agile responsiveness that continuous integration fosters. Strictly linear development is similar to the Waterfall approach and lacks the flexibility that characterizes Agile methodology. Thus, Agile is the methodology that truly benefits from and often includes continuous integration practices.