Skip to main content

Product

Optera uses the term product and not project on purpose. Scrum recommends having a product vision instead of a project vision. This is because the end goal is the realization of a product (with desired characteristics), not the realization of a project. A product is the development object that represents the desired solution or expected end result. It can be software, an application, a system, a service or even a physical product.

Product vision​

The product vision is a clear, concise description of what you want to achieve with the product. It provides a common direction and goal for all team members. It guides development decisions and serves as the basis for creating the product backlog. The product vision is maintained by the product owner and is regularly re-evaluated and adjusted as the product progresses and new information is discovered.

The product administrator can define the product vision from the product dashboard.

Product objective​

The product objective represents the desired result in the shorter term (usually a few sprints). It is a clear, concise statement that guides the team.

The product administrator can define the product objective from the product dashboard.

Epics​

Epics are the major groupings of elements in your product backlog. They can be used, for example, to define your product's major feature families.

Team​

The product team must be defined for the product. Product team members must be members of the organization.

Team members are assigned a role. They are presented below.

Product Administrator.​

The product administrator has access to the product parameters. He/she can also define the product's vision and objective. He also has all the rights of a team member.

Team member​

A team member has the right to edit backlog items. This is the normal role of team members.

Stakeholder / Guests​

It is also possible to invite stakeholders who will have read-only access and the ability to add comments on backlog items.

Product Owner and Scrum master​

For information purposes, the product owner and scrum master can be chosen from among the members of the product team.

Backlog items types​

Backlog items have a type. The type is used to classify backlog elements. By default, a Story and Bug type are created in scrum mode, and a Task type in simple mode.

Backlog item status​

Backlog items have a status assigned to them.

The statuses are : Backlog > To do > In progress > Done > Closed.

Backlog​

The backlog status can have upstream statuses to organize the product backlog. This allows you to display a Kanban for the product backlog with one column per status to organize the elements.

In progress​

The "in progress" status can be subdivided into different statuses, thus adding columns to the product kanban. It is possible to automatically assign an item to the user who places it in that status on the kanban. To this end, the auto assignment option on the status allows you to activate/deactivate this feature.

Account​

This feature allows you to restrict the accounts available for work logs. If no account is specified, all accounts are available on the product. Otherwise, only the account(s) listed are offered.

Basic parameters​

Working method​

The product can operate in 2 different modes. The "Scrum" mode is the most complete. It enables you to manage the product backlog, sprints, sprint reviews and retrospectives. The "simple" mode allows for simpler management without defining sprints. You can switch from one mode to the other, but sprints are permanently deleted when you switch from sprint mode to simple mode.

Estimate mode​

For each product, the estimation mode must be defined. You can choose between estimating in points or in hours. Estimating in points allows you to define a whole number according to a freely defined scale.

Restrict to team​

Makes the product available to team members only.

Enable release management​

Disables release management for products that do not work with releases.

Enable product backlog​

Only available for simple products. Disables product backlog for very simple products where kanban is sufficient.

Definition of "done​

You can define in text form what is meant by "done" for your product.

This text is then included in the Kanban so that members are aware of this notion and check when they finish a backlog item whether its state corresponds to this definition.

git checkout model​

If you're using git, you can define a specific template for the git checkout command. This will then allow you to copy this command from each backlog item.

Default account​

The default account defines which customer account will be initialized by default in the time management of product backlog items. Setting this information saves time when creating backlog items.