A release is ready when more than the build is ready. People need the right access, the application needs a tested route to production and someone needs to know what happens if the first users encounter a problem.

Test the journey that matters.

Confirm the agreed acceptance criteria on the supported devices and browsers. Include sign-in, the main task, permission changes and the important error states. Use representative data, not just the clean example from a demonstration.

Check the connections between components. A form that appears to work and an API that passes a separate test do not prove that the complete user journey reaches the intended result.

Confirm accounts and configuration.

Hosting, domains, store accounts and external services should have known owners. Confirm which environment will be released and how its configuration differs from the test setup.

Keep credentials out of the source repository and define how authorised people manage them. Record recurring service costs and the dependencies that could interrupt operation if an account expires or access changes.

Prepare the operating response.

Name the person who coordinates the launch and the person who receives reports afterwards. The support arrangement should say when help is available, how issues are raised and which situations require escalation.

Agree what will be monitored and how the team would respond to a failed release. Recovery or rollback procedures should match the actual application and its data changes, rather than appear as an untested line in a checklist.

Make handover part of delivery.

Gather the source code, design files, release notes and operating documentation promised in the scope. Identify known issues and distinguish them from future feature requests.

For mobile applications, submission is not the same as approval. Store review remains a separate dependency. For every platform, the next review should focus on real use and the highest-priority follow-up work.

Keep in mind

A release is a shared operating decision, supported by tested software and clear ownership.

Questions for the working session.

  • Has the core journey been tested in the release environment?
  • Who owns each account and recurring service?
  • Who responds to a problem, and through which channel?
  • Are the handover and recovery steps ready?
Download the app release checklist ↓Explore the related service →