Skip to main content

Deployment audit & DORA baseline

The before-photo that later proves RAPID's acceleration claim. Runs during STOP: map each product's real path to production, then baseline the four DORA keys. Without this baseline, "velocity compounds" is a slogan; with it, it's a measured delta.

The method​

  1. Map the real path to production — every step, including the manual ones. Manual steps are the "partial automated deployment" the deck names; naming them is the first fix.
  2. Baseline the four keys per product:
    • Deployment frequency
    • Lead time for change
    • Change-failure rate
    • MTTR
  3. Record — the baseline is captured before any RAPID work starts, so the post-RAPID comparison is honest.

Why it's a STOP task​

The CI/CD standard instruments these keys automatically going forward. But the legacy baseline has to be measured on the estate as it is today — that's a one-time STOP activity, and it's the denominator for every later claim about RAPID's impact. Feeds the metrics platform.

Standards referenced: DORA.