Features and themes

Group the stories that carry the same business value, called Themes on the business side.

A Feature groups stories that carry the same business value; it acts as an epic. In the Business view, it is called a “Theme”.

Create and rank Features

The Product Owner manages Features from the Technical view, Features view. Under New Feature, they enter:

• the Feature name, unique in the project;
• a Description;
• the Type: Functional, or Enabler for a technical foundation;
• the Business value, from 0 to 100;
• a Colour, carried by every attached story.

Each Feature gets a readable identifier, for example PORTAIL-F1. The Product Owner ranks them with the Move up and Move down arrows, and changes them with Edit.

Attach a story

In a story’s details, on the technical side, the Product Owner chooses its Feature from the list, or None to detach it. A done Feature no longer takes stories.

Feature status

A Feature’s status is calculated from its stories:

• To do while none is in progress;
• In progress as soon as one is;
• Done when all are validated.

The Product Owner can Close it by hand, only if none of its stories is still waiting to be validated. A Feature closed by hand can be Reopened; a Feature done because all its stories are validated stays done.

Group requests by theme

In the Business view, the Group by theme box sorts requests under their Theme’s name, then those with No theme. Grouping is optional: proposing, following and validating work the same way.

Technical stories

The team also creates technical stories from the Technical view, with New story and the Technical story type. They do not appear in the Business view. A request that its author changes into a technical story, from the Technical view, stays visible there: it comes from a request. A guest does not create technical stories.