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

Edit this flowarrow_forward
Software release processEngineering9QA2Release manager3Customers1YesNoRedeployGoNo-goYesNoFeaturemerged2Deploy tostaging3Run regressiontests?All testspass?5Fix thefailures?Go forrelease?Releasepostponed7Roll out to10% of usersWatch errorsfor 1 hour?Error ratenormal?11Roll back12Roll out toeveryoneRelease notespublishedReleasedoneReleaserolledback

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
1Feature mergedStartEngineering · step 2
2Deploy to stagingEngineering · step 3
3Run regression testsQA · step 4
4All tests pass?DecisionQA · Yes: step 6, No: step 5
5Fix the failuresEngineering · Redeploy: step 2
6Go for release?DecisionRelease manager · Go: step 7, No-go: step 8
7Roll out to 10% of usersEngineering · step 9
8Release postponedEndRelease manager · Done
9Watch errors for 1 hourWaitEngineering · step 10
10Error rate normal?DecisionEngineering · Yes: step 12, No: step 11
11Roll backEngineering · step 13
12Roll out to everyoneEngineering · step 14
13Release rolled backEndEngineering · Done
14Release notes publishedDocumentCustomers · step 15
15Release doneEndRelease 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_forward

How to get it right

  1. 1Run the same regression tests on every release. Skipping them 'just this once' is when releases break.
  2. 2Make go or no-go an explicit decision with a named owner.
  3. 3Roll out to a small share of users first and watch error rates for a set time before going to everyone.
  4. 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

See all 34 process flow templates