Backlog, what is it and how do you build it?
First of all, let’s start by explaining what a backlog is. A backlog is an evolving list of ordered and organized activities relating to a product or a service. It enables us to capture and manage the functionalities that the team intends to work on to meet a customer or user need. It is the essential tool for defining expectations with stakeholders and communicating activities to teams, which is very useful when we are designing a product. It also serves as a basis for planning, ensuring that all activities are taken into account.
The scope of the Backlog is dynamic, fed by feedback from users, market needs and technical constraints. So the content of our Backlog is constantly being adapted to ensure that it is functional. To better understand the structure of the activities in the Backlog, we can use the infographic created by Karyn Lurie, described in the article “A Deeper Dive into LEGO Bricks and Data Stories” by Brent Dykes. It draws an analogy between raw data with LEGO bricks that can be assembled to build a LEGO house, and data structured into a storytelling.
This regular review of the elements of the Backlog takes place during refinement events, during which we describe the next activities clearly and precisely, and estimate them. Less critical activities can remain vague, with a rough estimate that will enable the Backlog to be ordered. This sequencing enables us to ensure that the resources are mobilized optimally and that the activities with higher value are managed first.
The activities in the Backlog are organized regarding an implementation logic, linking them together, and in relation to the resources available, ensuring that they are allocated optimally in the time available. We speak of an ordered backlog rather than a prioritized one, in the sense that it follows a logical sequence, influenced by elements such as the business value of the functionalities, dependencies and risks. To illustrate this nuance, we can use the example of James Coplien of building a house. In our case, the Backlog contains all the elements that make up a house, such as the walls, doors, windows and roof. And the priority would therefore be the roof of our house. However, this order does not represent the way the house is built.Therefore we need to take this into account when organizing our backlog.
To conclude, the Backlog is a powerful tool for organizing and ordering the activities involved in producing a product. It’s important to keep it up to date by adding new elements, deleting those that are no longer relevant and adjusting their order according to needs and feedback. In this way, the Backlog is always in line with the progress of the product, to optimize all the work activities and maximize the chances of success!
