Project Management

3 Backlog Pitfalls to Avoid

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog


View Posts By:

Cameron McGaughy
Lynda Bourne
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Wanda Curlee
Christian Bisson
Ramiro Rodrigues
Yasmina Khelifi
Sree Rao
Lenka Pincot
Soma Bhattacharya
Emily Luijbregts
cyndee miller
Jorge Martin Valdes Garciatorres
Marat Oyvetsky

Past Contributors:

Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie

Recent Posts

Is Planning Predictive or Persuasive?

5 Ways to Up Your Mentorship Game

Lessons Learned on Digital Transformation

Murphy's Law: It’s a Call to Action, Not an Excuse

Emergent Strategy: How To Lead Now

Categories: Agile, Backlog, Priorities, Value

By Christian Bisson

A key artifact for any successful team is a healthy backlog: a list of what’s needed to bring value to the project—written in a way the team can understand and ordered so the team is always focused on what brings the most value.

Yet between all the user stories, enabler stories, technical stories, bugs, defects and so on, it can be quite challenging for a product owner to order all of this properly. 

Here are a few (ineffective) ways I’ve seen it done:

Pitfall 1: Prioritizing what’s understood

Product owners tend to be less technical, and not everyone can properly explain something technical in a way that conveys its value. The result is that items the product owner understands well are prioritized, leaving the other items on the side, which comes with a great long-term cost.

Pitfall 2: Going with instinct

I once heard the following about an item: Its value depends on how we feel that day. When people rely on pure gut feeling, the value of an item will vary depending on their emotions at the time. That means the decision of what will bring value to the product is more or less random, often resulting in leading the team to work on items that end up being pure waste.

Pitfall 3: Leaning into the noise

Some people even order their backlogs based on who complains the most! This merely encourages a culture in which whoever screams the loudest gets what they want.

So what works? There are many ways to take a more mathematical approach to giving value to items. What’s critical is to have an approach that allows the team to properly calculate the value of each item, regardless of what type of item it is. With clear guidelines, all three pitfalls can be avoided—and the decisions can be based on something more reliable.

How do you define the value of your backlog items?

Posted by Christian Bisson on: April 12, 2021 08:26 PM | Permalink

Comments (2)

Please login or join to subscribe to this item
Dear Christian
Very interesting the theme that brought to our reflection and debate
Thanks for sharing and your opinion
Who defines the value is the customer?
Despite this, it is important to avoid the pitfalls you mentioned

Please Login/Register to leave a comment.


"To stimulate creativity, one must develop the childlike inclination for play and the childlike desire for recognition."

- Albert Einstein