Software Release Process Flowchart
A release process from merged code to everyone: staging, regression tests, go or no-go, a staged rollout with monitoring, rollback and release notes.
4 teams15 steps3 decisionsFree download
Free to download. Edit it in Flow Studio to change the teams and steps, ask AI for changes, or export to PowerPoint, Word or draw.io.
Step by step
The same flow as a numbered list, ready for an SOP, a BRD or a ticket.
| # | Step | Who | Next |
|---|---|---|---|
| 1 | Feature mergedStartEngineering · step 2 | Engineering | step 2 |
| 2 | Deploy to stagingEngineering · step 3 | Engineering | step 3 |
| 3 | Run regression testsQA · step 4 | QA | step 4 |
| 4 | All tests pass?DecisionQA · Yes: step 6, No: step 5 | QA | Yes: step 6, No: step 5 |
| 5 | Fix the failuresEngineering · Redeploy: step 2 | Engineering | Redeploy: step 2 |
| 6 | Go for release?DecisionRelease manager · Go: step 7, No-go: step 8 | Release manager | Go: step 7, No-go: step 8 |
| 7 | Roll out to 10% of usersEngineering · step 9 | Engineering | step 9 |
| 8 | Release postponedEndRelease manager · Done | Release manager | Done |
| 9 | Watch errors for 1 hourWaitEngineering · step 10 | Engineering | step 10 |
| 10 | Error rate normal?DecisionEngineering · Yes: step 12, No: step 11 | Engineering | Yes: step 12, No: step 11 |
| 11 | Roll backEngineering · step 13 | Engineering | step 13 |
| 12 | Roll out to everyoneEngineering · step 14 | Engineering | step 14 |
| 13 | Release rolled backEndEngineering · Done | Engineering | Done |
| 14 | Release notes publishedDocumentCustomers · step 15 | Customers | step 15 |
| 15 | Release doneEndRelease manager · Done | Release manager | Done |
When to use it
Use it to agree how code reaches customers safely, and to give product and support a clear view of when a release is really done.
Who's involved
- Engineering9
- QA2
- Release manager3
- Customers1
Yours works differently?
Describe your own process in a few sentences and Flow Studio draws it, with your teams and your rules.
Describe your processarrow_forwardHow to get it right
- 1Run the same regression tests on every release. Skipping them 'just this once' is when releases break.
- 2Make go or no-go an explicit decision with a named owner.
- 3Roll out to a small share of users first and watch error rates for a set time before going to everyone.
- 4Publish release notes the moment the rollout completes, so support hears about changes before customers do.
Questions
What are the steps of a software release process?
Merge, deploy to staging, regression testing, a go or no-go decision, a staged rollout, monitoring, full rollout and release notes.
What is a staged (canary) rollout?
Releasing to a small share of users first, watching errors and key metrics, then rolling out to everyone if things look normal, or rolling back if they don't.
More process flow templates
- Incident managementAn incident response flow from alert to postmortem: triage, severity, incident lead, mitigation, status updates and closing the loop.
- IT change managementA change request flow with standard changes, change advisory board review, a scheduled change window, testing and rollback.
- Bug triageHow a bug report is checked for duplicates, reproduced, prioritised, fixed in a hotfix or the next sprint, and closed with the reporter told.
- Access requestHow an employee gets access to a system: manager approval, data owner approval for sensitive data, least-privilege access and regular access reviews.