Leaning Scrum for the first time can be a bit overwhelming. There are many new terms and concepts in Scrum. The backlog is one of those terms, and you may be wondering:
What is the backlog, and how is it used in Scrum?
Well, there are actually two backlogs in Scrum. And I’ll walk through both of them and why they matter in this article as we cover:
These two backlogs play essential roles for the Scrum team by providing clarity and safety for the team.
Have you ever asked a leader about the priorities, and they said something like, “It’s all top priority!” The order of the backlog sets the priority. There are no ties, and if one item is higher than the other, it’s more important. This clarity about priority empowers the team because they know they are doing the right work.
Having the backlog as the singular source of truth for what work should be done and what is priority provides enormous clarity and focus for the team.
If someone outside the team disagrees with the order of the backlog items, they can take it up with the product owner. This clarity of responsibility frees the team from burning time and focus on unnecessary debates.
The backlog items are usually written using a user story format. “As a… I want… So that…” This format identifies who they are building a feature for, what need it meets and what overall goal it achieves for the customer. This clarity of purpose equips team members to create value that doesn’t just check the box but makes a difference for the end-user.
I mentioned this earlier, but it bears repeating. The sprint backlog is all the team needs to focus on during a sprint. This clarity of focus provides a safe, closed environment that invites creativity, collaboration and innovative problem-solving.
Leaning Scrum for the first time can be a bit overwhelming. There are many new terms and concepts in Scrum.
Well we’re here to help.