Topic

Feature Roadmap


Response

The Product Owner is responsible for creating and maintaining the agile teams Feature Roadmap. The Feature Roadmap shows when the Agile team plans to deliver its primary unit of value, Features. Depending on the adopted Agile framework, each feature is accompanied by a number of associated product backlog items (including, Epics and User Stories). Each Feature life cycle must span the end to end life cycle. For example, incorporating, design, analysis, construction, release and adoption. Therefore, the entire Agile Team must focus on completing one Features at a time to minimise the amount of working progress, which allows value to be created as early as possible and delivered to the Customer for early evaluation.

The Feature Roadmap breaks the calendar into several time zones. Sprints, quarters, half-years and whole years.

To fully understand the primary purpose of a Feature Roadmap, it is important to appreciate how it differs from a traditional project plan. Traditional project plans, that take the form of a gantt chart is focused on tracking the completion of activities for a single discipline, for example, design or testing; whilst a feature roadmap focusses on tracking the delivery of value.

Each feature consists of all the disciplines that make-up the entire end to end life cycle. For example, incorporating, design, analysis, construction, release and adoption. The entire Agile Team focus on completing one Features at a time to minimise the amount of working progress, which allows value to be created as early as possible.

SCRUM Structure (Needs & Wants - Features - Epics - User Stories)

SCRUM Structure (Needs & Wants - Features - Epics - User Stories)

SAFe Structure (Epics - Features - User Stories)

SAFe Structure (Epics - Features - User Stories)


Discover more

Additional information, including working examples and templates are available in the Monetical knowledge base.

Contact us at info@monetical.com for further information and access.