Engineering / Software Delivery · Preview
Understand how changes reach production.
Connect delivery evidence to five DORA metrics for one service at a time. See the deployments, incident classifications and gaps behind each result.
Open Software DeliverySign in to your workspace. An owner or administrator sets up collection.
Five measures. Visible evidence limits.
Frequency and lead time use GitHub or GitLab deployment records. The remaining metrics need incident evidence and explicit deployment links; without that evidence, they stay unknown.
- Deployment frequency
- Successful production deployments per week, with the underlying deployment count.
- GitHub · GitLab
- Change lead time
- Median commit-to-production time, with p75/p90 and explicit commit-history gaps.
- GitHub · GitLab
- Failed deployment recovery time
- Impairment to recovery for deployment-caused incidents. Closing an issue or completing a rollback does not prove recovery.
- GitLab incident evidence required
- Change failure rate
- The share of deployments explicitly linked to production impairment. Unrelated outages are excluded.
- GitLab incident evidence required
- Deployment rework rate
- The share of deployments explicitly identified as unplanned corrections to production incidents.
- GitLab incident evidence required
Automate collection. Review ambiguous incidents.
Opted-in services collect evidence through the existing integration sync. GitLab incident collection requires separate consent. Explicit automation labels can supply incident classifications; owners and administrators can record audited corrections. A changed source record makes a previous review stale.
WardBee distinguishes source assertions from human reviews. A nearby deployment, a “hotfix” label or an issue closing is never enough to infer causality or recovery.
Start with a clear scope
This preview supports up to three services per connection, each with one repository and production environment. Snapshots cover up to 60 days. Provider history reads are bounded to 500 deployment records; larger or incomplete histories are reported as unavailable or partial.
AWS ECS runtime confirmation and PagerDuty/Jira incident collection are planned and are not available here. Delivery metrics do not change compliance control decisions or create a certification or performance ranking.