3 ms·
I think, way way down, it highlights these metrics: Deployment frequency: How often an organization deploys to production. Lead time for change: The time it t
by fatnoah 5y ago
I think, way way down, it highlights these metrics:
Deployment frequency: How often an organization deploys to production.
Lead time for change: The time it takes to get committed code to run in production.
Change failure rate: The percentage of production deployments leading to degraded service and remediation (e.g., rollback).
Time to restore service: How long it takes to fix a failure in production.
- ofrzeta 5y agoI don't understand how deployment frequency is a useful metric.
- ochronus 5y agoIt's not a silver bullet but in usual agile scenarios it's a good proxy for CI/CD health and velocity. Smaller, continuous daily deliveries usually mean easier experiments, testing, deployment, and rollback if something goes wrong (of course, depending on other factors). Metrics are not 'useful' in themselves, it's about how you use them. If you feel it doesn't make sense for your scenario, simply don't use it :)