Backlog, Roadmap and Prioritisation

Overview

The roadmap explains where we are going.

The backlog explains what we are doing next.

Prioritisation ensures that effort is focused on the highest-value work.

Roadmap

The roadmap should show:

• vision

• objectives

• major phases

• key milestones

• dependencies

• releases

• decision points

• risks

• expected value

Backlog

The backlog should contain:

• user stories

• technical tasks

• research tasks

• security tasks

• defect fixes

• operational tasks

• documentation tasks

• assurance tasks

Prioritisation Criteria

Work should be prioritised using:

• user value

• customer value

• risk reduction

• dependency impact

• security need

• commercial importance

• delivery effort

• urgency

• regulatory or contractual requirement

Definition of Ready

A backlog item is ready when:

• the objective is clear

• acceptance criteria are defined

• dependencies are understood

• required inputs are available

• the team understands the work

• the item can be delivered within the planned period

Definition of Done

A backlog item is done when:

• acceptance criteria are met

• quality checks are complete

• security requirements are satisfied

• documentation is updated

• evidence is recorded

• review or approval is complete where required