Your organization uses a change advisory board (CAB) to approve all changes to an existing service. You want to revise this process to eliminate any negative impact on the software delivery…

Question

Options

• AReplace the CAB with a senior manager to ensure continuous oversight from development to
• BLet developers merge their own changes, but ensure that the team's deployment platform can roll
• CMove to a peer-review based process for individual changes that is enforced at code check-in
• DBatch changes into larger but less frequent software releases.
• EEnsure that the team's development platform enables developers to get fast feedback on the

• A
  6% (2)
• B
  3% (1)
• C
  81% (25)
• D
  10% (3)

Explanation

DORA (DevOps Research and Assessment) research consistently shows that change advisory boards (CABs) are a predictor of lower software delivery performance because they create approval bottlenecks without improving reliability. To eliminate CAB's negative impact: Option C (peer-review based process at code check-in) replaces heavyweight committee approval with lightweight, developer-level code review - this is the DevOps best practice that maintains change quality while dramatically improving velocity. Option E (fast feedback from the development platform) - automated CI/CD pipelines with testing and deployment feedback - empowers developers to catch problems early, reducing the need for external gatekeeping. Option A (replace CAB with a senior manager) just moves the bottleneck to a single person, which is worse. Option B (developers merge their own changes) removes oversight entirely. Option D (larger, less frequent releases) is the opposite of what improves delivery performance - smaller, more frequent releases are safer and faster to recover from.

No community discussion yet for this question.