How should you define the first software release?

Short answer

The first release of custom software is the smallest working flow in which one user can complete one main task from start to finish. Define scope by behaviour rather than by screen count, keep dependencies visible and decide the next release from the need observed in first use.

Choose the core journey

The first release does not have to satisfy every department’s requests. Select a complete task for a specific user, such as submitting a request, approving a proposal and starting a project.

Write behavioural acceptance criteria

Replace “reporting will be included” with who receives which report from which data. Include unauthorised access, missing information and failure scenarios.

Expose dependencies

Third-party access, sample data, business rule approval and client-side responsibilities belong in the plan. Delays to these inputs affect development; keep unknowns visible.

Let usage inform the next release

Observe where users get stuck, which information is missing and where manual work remains. Choose subsequent features using actual needs as well as the original ideas list.

What stays out of the first release

The first release usually leaves out advanced reports, detailed settings screens, secondary roles and rare exception flows. Each of these should be written down as postponed in a decision record, so postponed work is not lost and the first release does not quietly grow.

A practical evaluation exercise

Define the first release as one complete task: an authorised user submits a request, an owner handles it and the result can be traced. Specify inputs and failure behaviour at each step. Defer advanced settings or reports for other tasks when they are unnecessary to validate this workflow. We also cover how to split a first release across web and mobile on our web and mobile app development page.

Frequently asked questions

Two questions we are often asked on this topic.

How long does a first release take?

It depends on the scope. How small the first release is kept determines the time; a time promise before the scope is clear is misleading. Once the scope is written down, a phased timeline can be given.

When should I show the first release to users?

As early as possible, when the first slice in which the main flow works is ready. Early use makes missing information and stuck steps visible without a large investment.