Backlog sprint – The part of the product backlog selected for implementation in the current sprint.
– Selected by the team based on priorities
– Digitalized so that you can see the daily progress
– During the sprint, the development team can add
– Items can only be discarded in consultation with the product owner
The sprint backlog is a kind of team commitment for the next iteration of the sprint (more about sprints in the next sessions). The product owner adjusts the customer’s expectations according to the team’s commitment. Therefore, only the product owner can throw some stories out of the sprint backlog during the iteration.
The team can add to the sprint backlog at any time on its initiative. Usually, the addition is not from the product backlog during an iteration, but because the team has identified new tasks that need to be completed to achieve the sprint goal.
As you recall, the stories at the top of the product backlog (the highest priority) are described and analyzed in more detail. These are the ones that go into the backlog of the next sprint.
How the product backlog differs from the sprint backlog
The main difference is that the product backlog is a complete list of requirements and tasks for the development of that very product. It is the framework that leads to the achievement of the main goal set.
The sprint backlog helps to visualize the process of working towards short-term goals. It is a list of tasks that need to be completed at a particular stage of development to realize one element of the product. The creation of the sprint backlog is led by the scrum team, not the product owner. Participants create a list of tasks at the beginning of each stage of the work.
How to create a product backlog
The backlog requires regular updates, as new competitors may appear in the process, market requirements, prices, and other factors that affect the functionality of the product being created may change. The product roadmap, user stories, and customer journey map are used to develop the product backlog. Let’s look in more detail at what each of these tools is needed for.
Product Roadmap. A document that shows the goals, the overall vision of the product, the direction of its development, and the main stages of development. It often lacks details but specifies deadlines for tasks, which allows you to set deadlines and calculate the time of work.
User Stories. It helps to describe the requirements of the product and better understand the users. It represents a brief history of what a potential customer wants to do, what results they expect to get, and why they need it.
Customer Journey Map. Visualization of the customer journey, his goals, emotions, and barriers. A map of the customer journey is generated for each specific User Story. CMJ helps to identify weaknesses, and correctly prioritize the work. The customer journey map and the roadmap and backlog are important to update and adjust regularly.
In the next article, we will find out what is the result of the team’s work in one iteration.
