1. Change Management vs CD advanced

    A regulated organisation's change management process requires approval for every production change, and the team wants continuous delivery. Are they compatible?

    2 min answer growwchange-managementcomplianceautomation
  2. Change Management vs CD advanced

    An enterprise change advisory process conflicts with continuous delivery. How can both requirements be met?

    2 min answer change-managementcdevidencerisk-classification
  3. Change Management vs CD intermediate

    Fastly's network pushes customer configuration globally in seconds, and that speed is part of the product. On 8 June 2021 a valid customer configuration change triggered a bug introduced by a deployment that began on 12 May, and about 85% of the network returned errors. After the incident someone proposes staging every configuration push in waves with a 10-minute bake. What does that buy and what does it pay?

    3 min answer fastlyconfigurationpropagationblast-radius
  4. Change Management vs CD advanced

    Most incidents in an organisation are caused by configuration changes rather than code deploys. How should configuration be versioned, canaried, validated and rolled back with the same rigour as code?

    3 min answer crowdstrikeconfigurationcanaryvalidation
  5. Change Management vs CD advanced

    The business mandates a code freeze for all of December, the highest revenue month. Engineering objects. Who is right?

    2 min answer riskreleasegovernance
  6. Change Management vs CD advanced

    Your CAB meets weekly and every production change needs approval. Lead time is 9 days, of which 6 are waiting. The board will not simply be removed. What is your approach?

    2 min answer governanceitildelivery