Pod Insights The Agile Daily Standup - AgileDad Why, When, and How Do We Clean a Backlog About this episode Why, When, and How Do We Clean a Backlog
Teams working in an agile way commonly use a backlog. However, teams often find that managing a backlog becomes more complex than expected once it begins to fill up.
We can agree on the importance of managing the backlog. When used properly, the backlog should be the core repository for requirements (with product backlog items referencing other artefacts as needed). Yet, it may contain needs and requests from various stakeholders, each with a very different perspective. If it transforms — paraphrasing Allan Kelly, in “Moving Away from Backlog Driven Development: A New Chapter in Agility? https://youtu.be/hrx6Teslz2E” — into a bottomless pit, we will lose sight of what is important.
How to connect with AgileDad:
- [website] https://www.agiledad.com/ https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/ https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/ https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 Teams working in an agile way commonly use a backlog. However, teams often find that managing a backlog becomes more complex than expected once it begins to fill up. We can all agree on the importance of managing the backlog. When used properly, the backlog should be the core repository for requirements with product backlog items referencing other artifacts as needed. Yet, it may contain needs and requests from various stakeholders, each with a very different perspective. If it transforms, paraphrasing Alan Kelly in Moving Away from Backlog-Driven Development, A New Chapter in Agility, into a bottomless pit, we will lose sight of what's important.
1:02 Speaker 00 So, how do we solve this? How do we question ourselves? What questions do we ask? How do we get to the point where we understand it better? I think the first question we need to ask ourselves is the backlog, has the backlog become a pit for everything? If the backlog is the only source when it comes to requirements and what teams will work upon to deliver features, it could also be true that there are many possible ways for an item to enter and be added to the backlog, I don't want to say erroneously, but without intent of ever doing it anytime soon.
1:34 Speaker 00 Because any stakeholder can be a possible source of a new backlog entry, it's easy to get a big list of requests that conflict with others and lack coherence. When that happens, your backlog becomes what many people refer to as the black hole or bottomless pit. So, the backlog should only include items that will help realize business value in the near future. That links to the organization's strategy. The items should contribute to a higher business goal or outcome, like an OKR. I think that if you have too many items, it means you usually don't have enough focus. It's common for people to treat the backlog as kind of a repository where everything just goes to sit, where we register every request, every win, desire, want, need from all the stakeholders in a project.
2:19 Speaker 00 This leads to classic backlog anti-patterns like oversized backlogs and expired items and things that people no longer need. Having a huge list of items in the backlog will certainly lead to a loss of focus and a loss of agility. So you need to be careful.
2:38 Speaker 00 Next question. Are items in the backlog truly aligned with the vision and strategy? Or are they just a shiny keys request? The backlog should be structured to include various types of requirements defined by IBA's BA Body of Knowledge, right? So they talk about business, stakeholder, and solution requirements. One way of approaching this is to structure the backlog into epics, features, and stories, respectively.
3:09 Speaker 00 If you do this, and you do it right, this will allow you to have traceability of the value that everything brings within a strategy that the organization found to be aiming towards its goal without losing focus on the prize at the end. So I think it's just a combination of things that has to be well-aligned, and in turn, that gives you a well-structured backlog. Make sure the backlog only has main goals and stories that contribute to those goals. Anything else is just noise.
3:44 Speaker 00 On a recent webinar series, Dr. Michael White suggests having only stories with a clear user problem in mind. Technical work should only appear in a backlog by exception when strictly necessary. Another common issue comes when adding non-functional requirements to the backlog. Dr. White suggested having them as acceptance criteria for a story, not an actual item. If a non-functional requirement crosses multiple stories, it should instead be one of the points of the definition of done checklist, not necessarily an item in the backlog. Another thing to consider is the item's age. The age of an item inside a backlog is also a possible indicator to value the item,
4:28 Speaker 00 or more likely, a lack of value. In a list of backlog management anti-patterns, one of the anti-patterns commonly found is outdated issues. And it suggests that the item has not aged beyond three iterations. I always say N plus two, right? If it's something that we're doing now or in the next two, we're good. When it hits the three, it's old. A similar indicator suggests that it's ideal between two and four months. I think that's too far out. You know, I just really believe if you're going to work on things, keep it in your near future. I always say the roadmap should be now plus the next two quarters. If we're trying to track sprints, it should be now plus the next couple of sprints. If we're trying to figure out what we're going to be doing during a sprint,
5:11 Speaker 00 it should be now in the next couple of days. I just always say N plus two because that formula works for me. Another thing that has to be a priority in backlog management is paying attention not only to what comes into the backlog, but also what moves out of the backlog. Paraphrasing another interesting metaphor, moving away from backlog-driven development. If we can imagine a backlog to be like a mortgage, then more stories mean more interest is paid. You're supposed to eventually pay all of the loan, including the interest. You do not want debt that just continually increases. So if we treat backlog like a mortgage, you gotta pay it down.
5:55 Speaker 00 There's an interesting method that you can use to help from falling into some of these traps. They have something called a rock crusher. It's a model for flow-based backlog management. It's one method of managing backlog items into a funnel in the most fluid way. And for that, it crushes rock. A rock is an item within the backlog. Throughout the funnel, prioritization is constant. The perceived value maintains the rock inside of the funnel and next to the state, in, to the next stage. If not, one throws it out into a wastegate. The method has a specific ceremony where the group decides what to throw away and what to keep, called a crush meeting. It's kind of interesting.
6:39 Speaker 00 It's very similar to backlog refinement meetings in Scrum. I was just about to say that being a funnel should flow it begins by by having the larger rocks function at the top, but arrives at a point where only the smaller rocks can pass through larger rocks. Don't make it through. And an interesting thing about this method is it obligates throwing away items from time to time. In this crush meeting, which team decides, uh, what team decides to do and send rocks to the to wherever they belong, whether they belong to project or waste gate, something is always are almost always sent to waste gate. Interestingly, if nothing goes away, it's seen as an anti-pattern. You
7:22 Speaker 00 don't you want to make sure you're at least getting rid of some things and keeping that backlog clean. What I'm trying to say is keeping a tidy backlog is by far one of the hardest things you can do. That's why it's step number four in the 12 step program. I believe that if you really put dedication and focus towards it, that you can wind up doing a better job. That's going to do it. I hope you enjoyed this episode. If you have a topic you want us to discuss, learn more natural dad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well and stay agile, my friends. Until next time, do take care. Bye now.
Previous How Are You Today? I'm Fine, Thanks... Next Corporate, Business or Functional Strategy? Page updated November 6, 2026 · transcript and summary are machine-generated