Backlog is ... Definition, characteristics, features, example

Backlog is a work in progress magazine. Its contents and accessibility are the responsibility of the product owner. This is the only source of any changes to the product.

A backlog is a list of new features, changes to existing features, bug fixes, infrastructure changes, or other actions that a team can take to achieve a specific result. He is the only authoritative source of information on which the company relies. This means that nothing will be made of what is not in this journal. It represents the option of working on a product that a team has to achieve a specific result.

Specifications

Adding a product element to the work in progress journal should be quick and easy, and just as easily that element can be removed from the backlog that does not lead directly to achieving the desired result or does not allow progress to achieve the result.

Backlog items are accepted in various formats, with user stories being the most common. The team identifies the format they have chosen and considers the backlog items as a reminder of the aspects of the solution they are working on.

Product backlog

The journal of outstanding works allows each employee of the unit to submit ideas for improving the product or service. The prioritization process determines what actually becomes part of the product. This method allows you to implement tasks, spending resources only on the best ideas available at the moment. In case of abandonment of outdated ideas, the backlog is sometimes supplemented and refined.

The product backlog varies in size and granularity to a large extent from how soon the team starts working on it. Those tasks that the team will work in the near future should be small in size and contain enough details so that work can be started. The group can establish a definition of readiness, indicate their wish regarding the information that they would like to have in order to begin work on the backlog.

The backlog sequence of a product changes as the team better understands the results and finds a solution. This reordering of existing elements, the constant addition, removal and refinement of these elements determines the dynamic nature of the backlog.

Kinds

Backlog of programs

It is expected that the programs will fulfill the requirements of stakeholders and plan their implementation as projects. This usually happens on an ongoing basis. The backlog structure is useful for storing requirements, prioritization and planning processes, according to which requirements of high importance are grouped into projects.

Backlog of tasks

It can be implemented by an individual or team as a time management method. People have a limited amount of time and often need to prioritize tasks. As with products and programs, you can expect that not everything in the backlog will be completed.

Who selects tasks for backlog?

The responsibility for the content of the backlog lies with the owner of the product. Of course, he is not alone in his task and can ask for any help he needs. The product owner must have a good understanding of the customer and be in close contact with him. He can and should also always communicate with other interested parties in order to take into account their wishes. It is also important to keep in touch with the development team to understand the cost and complexity of certain requirements.

But in the end, the product owner is the only person responsible for prioritizing. This is also the reason why there should never be multiple product owners or product owner committees. For decision-making there must be a single point of truth - this is the owner of the product. It collects all the information about the market, business, stakeholders, difficulties, etc. into one clear definition of priorities.

The team working on the product can play a role as the owner of the product with a primary responsibility - maintaining the product. Key actions to maintain a backlog are prioritization of items of outstanding product obligations, deciding which items of outstanding items should be removed from the backlog, and helping to clarify the failed work.

What does it look like?

Backlog is an effective way for a team to communicate what it is working on and plans to work on. Story maps and information sources can provide a clear picture of the current situation for the team and stakeholders.

A backlog can be presented in physical form using registration cards or notes, or it can be presented in electronic form, for example, a text file or an Excel spreadsheet. An electronic form is the best option for a team that has remote members or collects a lot of additional product information. Physical forms provide the advantage that the product reserve is constantly visible and specific during discussions related to the product.

Backlog Features

After the product backlog is created, it is important to maintain it regularly in order to keep up with the program. Product owners should check the backlog before each operation planning meeting to ensure that they prioritize and include feedback on the latest operation.

After the backlog is increased, product owners should group it into short and long term positions. The nearest tasks should be fully specified before they are marked as such. This means that complete user stories have been compiled, collaboration with design and development has been settled, an evaluation of the development has been made. Longer-term elements may remain a bit vague, although it would be nice to get a rough estimate from the development team to help prioritize.

Backlog is the link between the product owner and the development team. The product owner can at any time change the priorities of work in the queue due to customer reviews, clarifying ratings and new requirements. However, once work begins, changes should be minimized, as they disrupt the work of the development team and affect focus and morale.

Errors in Maintenance

There are several main mistakes when maintaining a backlog, which you need to closely monitor:

• The product owner prioritizes the backlog at the beginning of the project, but does not adjust it as feedback from developers and stakeholders is received.
• The team limits backlog to those elements which are focused on the client.
• It looks like a document that is stored locally and rarely used, which prevents stakeholders from updating.
  

Backlog Example

To work with the backlog you do not need to use any complex tools. You can start with paper cards or with a Microsoft Excel spreadsheet.

The most common way to identify backlog items is through a user story. In this case, you can add a name for a quick link (however, when using account cards this is usually not done), and if necessary, add conditions of satisfaction on the back of the card.

• Automatic beer selection for a party. The buyer wants to impress his friends with a multitude of rare brands.

• A selection of new beer to taste. The buyer wants to see a beer catalog to choose a new one. He can see various tastes right on the catalog pages.

• Order your favorite beer. A regular customer wants to see their favorite beers in order to order them again each time.

• Recommend an expensive beer. The store owner wants the bar to recommend expensive beer in order to increase his profits.

If desired, you can also add several optional fields, such as "Number", "Rating", "Conditions" and "Priority" (which can be used to sort the backlog in order of business priority).

As you can see from this example, the product backlog does not need any sophisticated tools. An Excel paper card or sheet is more than enough to take care of a sufficiently deep and capacious backlog and determine its clear position.