Continuous Delivery requires Release Orchestration
no recording on file
summary
Argues that achieving Continuous Delivery needs release orchestration across the organization rather than just new tools. Covers coordinating speed, market-driven relevance, and built-in quality by changing product architecture, build/test practices, and involving middle managers, architects and team leads in cross-team release coordination.
AI-written summary · about
related talks
38mContinuous Delivery, or the magic button for on‑demand releases
30mModern Continuous Delivery
19mModern Continuous Delivery
59mWhy Continuous Delivery doesn't work?
38mContinuous Delivery, or the Magic Button for On‑Demand Releases
34mArchitecting for Continuous Delivery
48mContinuous Delivery: Tales from Windowsland
24mWhy, What, and How of Continuous Delivery