Skip to main content

Product backlog

The product backlog is an ordered list of all the features, requirements, enhancements and fixes needed to develop the product. It represents the product vision and is maintained by the product owner. The product backlog evolves throughout the project as new requirements are identified, priorities change and new information is discovered.

Backlog items are prioritized, with the most important and highest-value items for the customer at the top of the list. This enables the team to focus on the most critical items from the very start of the project.

Optera also lets you add additional columns to your product backlog. This allows, for example, a column for ideas, another for items to be evaluated, a 3rd for items in preparation, and so on. For a product backlog containing many elements, this makes it easier for the Product Owner to see which elements are "ready" for the next step, and which still need preparation (analysis, breakdown, estimation, etc.).

Product backlog management​

Product backlog management is a joint task between the product owner and the product team. The product owner is responsible for defining, prioritizing and maintaining backlog items. The team, for its part, is responsible for estimating the complexity and effort required for each backlog item.

However, Optera does not limit editing to the product owner alone. The whole team can add or modify backlog items.

From the product backlog management screen, users can quickly add items and manage item prioritization by drag & drop. By clicking on the [+] button of each item, it is possible to edit the item.

Backlog item​

The product backlog can contain a variety of elements such as user stories, bugs, tasks, enhancements, regulatory requirements, and much more. These elements can vary in level of detail depending on their nature and context. The aim is to adjust the level of detail according to the needs and progress of the project. Items of higher priority or planned for the short term may be described in greater detail, while those planned for the longer term may be more succinct and abstract, allowing flexibility in adjustment and subsequent planning.

Title and reference​

Backlog items have a mandatory title and an automatic reference. This makes it easy to find items quickly.

Item description​

The item description is formatted text. It can contain links and images.

Mentions​

The description may mention another backlog item. By entering the "#" character, other elements of the project backlog will be proposed.

It can also mention a user in the organization. Enter the @ character to display the list of users.

A mentioned user receives a notification.

Meta data​

Type​

Element type, according to the types defined in parameters.

Status​

The status of the backlog item, according to the status defined in the parameters.

Assignee​

The person assigned to the item.

Reporter​

The person who reported the item. By default, the person who created the item.

Epic​

The element's epic. Epics are defined in parameters.

Tags​

Tags, also known as labels, can be added to backlog elements to provide additional classification and organization. Tags are keywords that can be used to group and categorize backlog items according to different criteria. It is then possible to filter backlog elements according to tags.

Fix versions​

Version(s) that include(s) or correct(s) this item.

Affected versions​

The version(s) affected by this item. Generally used to indicate which versions are affected by a bug.

Versioning​

If the git checkout model is enabled, a button will be available under this tab to copy the checkout command. If git integration is enabled, a summary will be displayed in this tab.

Work​

Estimate in hours or points​

Depending on the evaluation mode of the product, the field lets you enter the estimate in points or hours.

Need estimate​

Mark the backlog item to be estimated, to find it in the list of estimates.

Total work​

Total recorded work is displayed under this heading.

Default account​

The default account proposed when recording a work log. This account is initialized according to the account defined on the product.

Value​

Priority​

Allows you to define the priority of the backlog item. This can be used to help you order product backlog items.

Business Value​

Defines the value of the backlog item. This can be used to help you order product backlog items.

Attachments​

List of documents attached to the backlog item. Drag and drop files into the area provided to add them. You can also copy/paste images into the description (or comments) to add attachments.

Allows you to define links between backlog elements. Can be used to indicate that one element blocks another, causes another or that 2 elements are similar or related.

Sub-elements​

Backlog elements can be broken down into sub-elements for better management and greater precision of the tasks to be carried out. This feature adds extra granularity to elements, breaking them down into smaller, more specific steps.

By breaking down backlog items into sub-elements, the development team can gain a more detailed view of each task and better plan its execution.

In the context of the product backlog and sprint planning, only the parent element is presented.

Once the sprint has started, however, in the kanban, the team works directly with the sub-elements.

The sub-elements take on the type and epic of their parent. They do, however, carry their own assessment of work and value.

Sub-elements are always in the same sprint as their parent, unless they are in a closed status.

Comments​

Comments enable exchanges between team members and also with stakeholders. They can contain links and images. It is also possible to make mentions.

Updates​

Chronological list of updates made to the backlog item.

Work logs​

Tab allowing entry and modification of work time performed on the backlog element. Each entry includes the date, an account, a comment and the working time.