WHY CI/CD (Continuous Integration/Continuous Delivery)?
- Longer release cycles (“waterfall projects”) have dramatically higher overhead than more frequently released (“iterative” or “agile”) shorter cycles.
- As a release begins, a quality assurance team is prepared, waiting for things to test, and IT does not have anything to deploy.
- Towards the end of a release cycle, QA is running at full force, as is IT, but development is split between bugs and planning the next major release. Context switches are frequent.
