Fuelling delivery – the lean guide

We’ve structured the FUEL framework from the viewpoint of the UX and BA members of the Customer Team and from the Agile perspective that the PO will orchestrate (although the PO is concerned with the entire process, of course).

Frame the opportunity

What is it?

The opportunity is explored at a high level from a number of perspectives. Who are the users, what problems do they have that the opportunity aims to solve, what are the current workarounds, what value will the users get from the proposed opportunity?

Why do it?

It’s important to understand what the opportunity in broad terms and determine whether or not it is worth pursuing. It is likely a number of possible opportunities exist and developing an understanding of which is most valuable, usable and feasible helps you prioritise your efforts.

UX/BA focus

  1. Conduct initial research
  2. Develop problem statement

Agile focus

  1. Understand relative value and likely cost of delivery (VROM)

Understand users and options

What is it?

Building on the understanding gained when framing the opportunity, a more detailed picture of the users and their specific needs is explored and a detailed picture of the options available to address the opportunity is developed.

Why do it?

This is the opportunity for the team to understand in greater detail the user’s goals and the ways in which these might be met – how the value will be delivered. The assumptions developed at this stage form the basis of the tests that will help shape the team’s understanding.

UX/BA focus

  1. Conduct discovery research
  2. Identify and develop hypothesies

Agile focus

  1. Define assumptions and risks
  2. Prioritise options and define Epics

Envision solutions

What is it?

The most promising options are developed into testable journeys and prototypes. During this phase the MVP is increasingly driven out through the collaborative design process. The cost of delivery of each solution versus the expected value that will be delivered is roughly estimated.

Why do it?

Developing an understanding of the solutions that are likely to deliver the required value enables the team to identify the most usable and feasible options. It is also important to concentrate effort on the most promising options so that learning in the next phase is focussed.

UX/BA focus

  1. Develop process flows
  2. Define content requirements
  3. Develop prototypes and walkthroughs

Agile focus

  1. Define costs (ROM)
  2. Develop and slice User Stories
  3. Define metrics

Learn and validate

What is it?

The possible solutions are tested with target users and feedback is incorporated into designs. The MVP is established, the value of the opportunity is validated and the expected cost of delivery determined.

Why do it?

Until solutions are tested with users the assumptions leading up to this point remain just that, assumptions. Whether developing an Alpha, Beta or managing a live service, this is the point at which the conceptual work is validated and further options fed back into the pipeline.

UX/BA focus

  1. Test prototypes
  2. Iterate and retest designs

Agile focus

  1. Establish delivery backlog