Skip to main content

Adopt iterative, risk-based approaches

Last updated: 21 March 2025

Deliver value early through Minimum Viable Products (MVPs) and fast feedback cycles, applying appropriate testing at the right time to build sufficient confidence.

Motivation

Value for our users is only realised when they can start using the software, so we should try to release that value to them quickly. Our testing approach should be proportional to the risks of doing this – both in terms of impact to our users and to the organisation – rather than always applying the same approach in different situations.

Once we have insights from our users, we can better prioritise the remaining incremental improvements based upon both quantitive and qualitative data, rather than relying upon project roadmaps.

Applying this principle

  • Work with stakeholders to help them understand the opportunities to release an MVP that can be incremented.
  • Ensure that you have repeatable, automated build pipelines that include appropriate automated tests.
  • Reduce the reliance upon end-to-end testing by building confidence early through faster, cheaper means of testing including automation.
  • Support stakeholders in identifying, understanding, mitigating or accepting the risks of each release.