What is Continuous Integration/Continuous Deployment in Agile?

CI/CD are engineering practices that enable Agile's goal of delivering working software frequently. Continuous Integration (CI): developers integrate code changes into a shared repository multiple times daily. Each integration triggers automated builds and tests. Benefits: detect integration conflicts early, reduce "integration hell" at release time, maintain a consistently working codebase. Continuous Delivery (CD): every code change that passes CI is automatically deployed to a staging environment and can be released to production on demand with one click. Continuous Deployment: every passing change is automatically deployed to production without manual intervention. CI/CD supports Agile by enabling: Sprint-end deployments (potentially every 2 weeks), feature flags for incremental rollouts, rapid feedback from production, reduced manual testing burden. Without CI/CD, Agile teams often face a "last mile" problem: code is written Agile but release is Waterfall (a long integration and testing phase at the end). CI/CD removes this bottleneck.