diff --git a/flow.md b/flow.md index 5c38038..051fc8f 100644 --- a/flow.md +++ b/flow.md @@ -18,7 +18,7 @@ capture the answers: | **Question** | **Tired (1)** | **Inspired (5)** | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | 1\. **Cycle Time** - How long does it take for a code change to go from version control to running in Production? (Minimum, Typical) | 2 weeks or more | 1 hour or less | -| 2\. **Deployment Frequency **- How often does your team deploy to Production? | Every 2 weeks or longer in practice | Every 2 days or less | +| 2\. **Deployment Frequency** - How often does your team deploy to Production? | Every 2 weeks or longer in practice | Every 2 days or less | | 3\. **MTTR** - How long does it take to restore your application or service after an incident? | We have no idea - we do not track this | We track MTTR and we restore service in 10 mins automatically and test this in the deployment pipeline | | 4\. **Failed Changes** - What proportion of changes to your application or service in Production fail or need remediation? (This is typically the number of failed deployments) | More than 20% of our changes/deployments fail in Production | Less than 5% of our changes/deployments fail in Production | | 5\. **Queue Length** - How many things does your team work on at the same time? (Minimum, Typical) | We have significantly more Work In Progress (WIP) items than team members | We have explicitly limited our WIP based on queuing theory (or Cost of Delay) and the WIP is equal to or less than the number of people in our team |