2024 Author: Howard Calhoun | [email protected]. Last modified: 2024-01-17 18:37
Backlog is a work in progress log. Its content and availability are the responsibility of the product owner. This is the sole source of any changes made 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 certain result. It is the only authoritative source of information that the company relies on. This means that nothing will be done from what is not in this log. It represents the way the team has to work on the product to achieve a specific result.
Features
Adding a product item to the work-in-progress log should be quick and easy, and just as easily removed from the backlog is an item that does not lead directly to the desired result or does not allow progress to be achieved.
Backlog items are accepted in a variety of formats, with the mostcommon are user stories. The team determines the format they have chosen and treats the backlog items as a reminder of aspects of the solution they are working on.
Product backlog
A backlog allows everyone in the department to contribute ideas to improve a 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 largely on how soon the team starts working on it. The tasks that the team will be working on in the near future should be small in size and contain enough detail to get started. The group can set up a definition of readiness, indicate their desire for the information they would like to have available in order to start work on the backlog.
The product backlog sequence 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.
Views
Program Backlog
Programs are expected to meet stakeholder requirements and plan to implement them as projects. This usually happens on an ongoing basis. The backlog structure is useful for requirements storage, a prioritization and planning process whereby high value requirements are grouped into projects.
Task Backlog
It can be implemented by an individual or a team as a time management method. People have a limited amount of time and often have to prioritize tasks. As with products and programs, not everything in the backlog can be expected to be completed.
Who chooses tasks for the backlog?
Responsibility for backlog content lies with the product owner. Of course, he is not alone in his task and can ask for any help he needs. The product owner must understand the customer well and be in close contact with him. He can and should also always communicate with other interested parties to take into account their wishes. It is also important to keep in touch with the development team in order to understand the cost and complexity of certain requirements.
But at the end of the day, the product owner is the only person responsible for setting priorities. 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 – the product owner. It gathers all information about the market, business, stakeholders, complexities, and more into one clear prioritization.
The team working on the product can play an owner roleproduct with primary responsibility - maintaining the product. Key backlog maintenance activities include prioritizing product backlog items, deciding which backlog items to remove from the backlog, and facilitating backlog clarification.
What does it look like?
The backlog is an effective way for a team to communicate what they are working on and what they plan to work on next. Story maps and information sources can provide a clear picture of the current situation for the team and stakeholders.
The backlog can be presented in physical form using index cards or notes, or it can be presented in electronic form such as a text file or an Excel spreadsheet. An email form is the best option for a team that has remote members or collects a lot of additional product information. Physical forms have the advantage that the product backlog is constantly visible and specific during product-related discussions.
Backlog features
Once a product backlog has been created, it is important to maintain it regularly to keep up with the program. Product Owners should review the backlog before each Operation Planning Meeting to ensure that the prioritization is correct and feedback from the last operation is included.
After the backlog grows, product owners mustgroup it into short-term and long-term positions. Tasks that are closest in meaning must be fully specified before they are marked as such. This means that complete user stories have been written, design and development collaborations have been established, development evaluations have been made. Longer term items may remain a bit vague, though it's good to get a rough estimate from the development team to help prioritize.
The backlog is the link between the product owner and the development team. The Product Owner can reprioritize work in the queue at any time due to customer feedback, refining estimates, and new requirements. However, once work begins, changes should be kept to a minimum as they disrupt the development team and affect focus and morale.
Dribbling errors
There are a few common backlog mistakes to watch out for:
- The product owner prioritizes the backlog at the start of a project, but does not adjust it as feedback from developers and stakeholders comes in.
- The team restricts the backlog to customer-facing items.
- It looks like a document that is stored locally and rarely used, which prevents interested parties from updating.
Backlog example
Forworking 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 define backlog items is through a user story. In this case, you can add a name for the quick link (however, this is usually not done when using index cards), and, if necessary, add conditions of satisfaction on the back of the card.
Automatic beer selection for the party. The buyer wants to impress his friends with many rare brands
Choosing a new beer to taste. A customer wants to look at a beer catalog to select a new one. He can see different flavors right on the catalog pages
Order your favorite beer. A loyal customer wants to see their favorite beers so they can order again every time
Recommend expensive beer. The shop owner wants the bar to recommend expensive beer to increase its profits
You can also optionally add a few optional fields such as "Number", "Rating", "Conditions" and "Priority" (which can be used to sort the backlog in order of business priority).
| Number | Task | Rating | Condition | Priority |
| 234 | Auto selection of party beer | 20 | Order | 1 |
| 556 | Choosing new beer to taste | 8 | Order | 15 |
| 123 | Order your favorite beer | 3 | Order | 40 |
| 89 | Recommend expensive beer | 5 | Profit | 50 |
As you can see from this example, a Product Backlog does not require any complex tools. A paper card or Excel sheet is more than enough to take care of a sufficiently deep and capacious backlog and define its clear positions.
Recommended:
The difference between a branch and a representative office: definition, concept, characteristics, features and working conditions
Many people often confuse the concepts of “branch” and “representative office” and use them in a synonymous connotation, but there is still a difference between these terms, which will be discussed in this article. You have probably heard such concepts as "separate subdivision", "branch", "representative office"… What is the difference? This information can be useful for any person, because you never know what will happen to you tomorrow. So, what is the difference between a branch and
What is a project. Definition of the project, its features and characteristics
The word "project" (projectus) is translated from Latin as "outstanding, moving forward, protruding." And if you reproduce the concept of "project definition" in the Oxford lexicon, you get: "a well-planned start of a business, a personally created company, or a joint work aimed at achieving specific goals"
Low pressure heaters: definition, principle of operation, technical characteristics, classification, design, operation features, application in industry
Low pressure heaters (LPH) are currently used quite actively. There are two main types that are produced by different assembly plants. Naturally, they also differ in their performance characteristics
Railway track is Definition, concept, characteristics and dimensions. Train dimensions and features of track facilities operation
Traveling by train through cities and towns, you can learn a lot of interesting and amusing things about the world of the railway. More than once, traveling people have asked themselves questions about where this or that railway track leads? And what does the engineer who manages the train feel when the train is just starting off or arriving at the station? How and from where do metal cars move and what are the ways of the rolling stock?
The effective interest rate is Definition, calculation features, example and recommendations
As part of the analysis of a loan (or investment), it is sometimes difficult to determine its true value or profitability. There are different terms that are used to describe rates or profitability. For example, we can talk about annual percentage yield, effective and nominal rate, etc
