Rethinking Product Backlog: Navigating Through the Weeds of Complexity

The Product Backlog is a critical asset in Agile product development; it represents a dynamic lean inventory of everything the product needs. For those of us navigating the multifaceted landscape of product development, there is often an impulse to seek an ideal structure for the Product Backlog. The familiar hierarchy of Initiative->Epic->Feature->User Story->Task/Bug is a common schema. However, before embracing this structure as a silver bullet, it’s imperative to critically evaluate the implications of imposing a hierarchy on the Product Backlog and to recognize the nuanced dynamics of working in complex environments. In this article, I will examine the delicate interplay between Product Backlog management and the intrinsic nature of complex systems. 


In conclusion, while the allure of hierarchy in the Product Backlog might be tempting, it is imperative to recognize that this may not be the panacea it seems. Complex product development demands a more nuanced approach. This entails acknowledging the fluid nature of complex environments, valuing emergent practices over best practices, and empowering teams to harness their expertise. By doing so, we move towards creating not just successful products but also fostering a culture that is adaptable, innovative, and resilient in the face of complexity.

The Illusion of Order: The Lure of Hierarchy

Hierarchy appeals to the human psyche because it seems to present a sense of order and control, especially in the face of complexity. However, this allure of hierarchy can be deceptive. In practice, hierarchy can introduce rigidity, create barriers to communication, and obfuscate what’s genuinely significant in the Product Backlog.

In essence, when the Backlog is cluttered with levels of hierarchy, it diminishes its transparency and malleability. It is critical to appreciate that the Product Backlog should generally encompass value. This is not to say we should dispense with additional content that provides context or clarification. Indeed, collateral materials such as wikis can be invaluable in offering insights. However, incorporating these directly into the Product Backlog does not add value and instead restrains the Backlog’s fluidity and transparency.

A Primer on Complexity

As a side point, engaging in a dialogue about the nature of complexity is imperative whenever the concept of “best practice” is brought up in discussions. Complexity is not just a buzzword; it’s a theoretical framework for understanding how different system components interact. In complex environments, it is impossible to predict outcomes with certainty due to the interdependencies and interactions among the components. This is a far cry from simple or complicated environments, where cause-and-effect relationships can be determined.

From the Cynefin Institute on

In simple environments, “best practices” exist because they offer tried and true methods for known problems. However, there are only emergent practices in complex environments where doing the same thing again can often have very different results. These practices cannot be predicted upfront and may only be effective temporarily. The most pragmatic approach in such environments is to start with a hypothesis, experiment, and be prepared to evolve the practice based on feedback and learning.

Ghosts from the Past: The Work Breakdown Structure

One of the reasons that hierarchy is so enticing is that it has historical roots in the traditional project management approach known as the Work Breakdown Structure (WBS). The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team. While the WBS was valuable in certain contexts, its hierarchical nature is not conducive to the Agile philosophy, which values responsiveness to change over following a plan.

Work Breakdown example

A work breakdown structure (WBS) visually organizes project deliverables into different levels based on dependencies. It’s essentially your project plan in a visual form, with your project objective at the top, then dependencies and sub-dependencies below. -Alicia Raeburn, Asana

Interestingly, the very presence of a hierarchy resembling the WBS within the Product Backlog may lead to individuals subconsciously reverting to old habits. This is not surprising as the human psyche finds comfort in familiarity; there is a tendency to revert to what we know. This, however, is akin to trying to fit a square peg in a round hole, as opposed to rethinking the fundamental paradigm of managing work.

A simple question to ask yourself when you open an item on your backlog is this:

“Does this item from my backlog, on its own, represent some value to the business? Can it be delivered independantly?”

If the answer is no, it’s not a backlog item but a work task!

The Flat Landscape: A Paradigm Shift

Instead of obfuscating the Product Backlog with layers of hierarchy, consider streamlining it to encompass just the work pertinent to the team.

 You can still employ tags, wikis, and attachments to provide context. This approach liberates team members to structure the Backlog in a way that makes sense to them and is responsive to the fluid nature of complex product development. 

I think it’s worth highlighting that strategy should inform but not dictate the choices made in organizing the Product Backlog. This is a crucial point. The reason organizations hire skilled individuals is to leverage their expertise and insights. There is a recognition that those closest to the work often have the most meaningful insights into what needs to be done.

Complexity and Cognition: The Human Factor

In complex product development, human cognition is a significant factor. Individuals and interactions are central to Agile principles. People come with diverse backgrounds, experiences, and perspectives. These differences can be a source of creativity and innovation. By flattening the Product Backlog, we create an environment where the team’s cognitive diversity can flourish.

Furthermore, in complex systems, a practice known as sensemaking becomes critical. Sensemaking involves assimilating information, interpreting it, and making informed judgments. A flat Product Backlog supports sensemaking as it reduces cognitive overload and allows individuals to focus on what’s truly important.

Strategy and Autonomy: The Balancing Act

The relationship between strategy and the Product Backlog is subtle. The strategy should serve as a compass, providing direction and purpose, helping us orienteer to our destination. However, it should not be a straitjacket. The dynamism of complex environments requires that teams have the autonomy to make decisions and adapt as necessary. There needs to be a balance between strategic alignment and autonomy. This balance is vital for harnessing the collective intelligence and creativity of the team.

Ultimately, the goal is to create a resilient, adaptable ecosystem capable of thriving amidst the uncertainties of complex product development. This involves creating flexible structures, fostering a culture that values learning and adaptation, and equipping teams with the autonomy to make decisions.

What’s in your backlog?

Upcoming Training Opportunities

These are the next five classes we have, and you can check out our full public schedule of classes.

Immersive Professional Scrum Product Owner with Russell Miller over 8 weeks starting 11th October 2023
Virtual Immersive
11 Oct-13 Oct, 2023
09:00-13:00 EDT
8 weekly half-days
Immersive Applying Professional Scrum with Simon Bourk over 10 weeks from18th October 2023
Virtual Immersive
18 Oct-20 Oct, 2023
09:00-13:00 EDT
10 weekly half-days
Immersive Professional Agile Leadership Essentials with Joanna Płaskonka Ph.D. over 7 weeks from 20th October 2023
Virtual Immersive
20 Oct-1 Oct, 2023
09:00-13:00 BST
7 weekly half-days
Live Virtual Product Backlog Management Skills with Joanna on 2nd November 2023
Virtual Traditional
2 Nov, 2023
09:00-17:00 GMT
1 full-days

We can deliver any of our courses as private in-house training over Microsoft Teams & Mural. We also recommend training based on your accountabilities or role, you can go directly to recommended courses for Scrum MastersProduct OwnersDevelopers and Agile Leaders.

Create a conversation around this article

Share on Facebook
Share on Twitter
Share on Linkdin

Related Courses

Scrum Master


An interactive activity-based course where students gain a strong understanding of Professional Scrum and the role of the Scrum Master.

Product Owner


Being a professional Product Owner encompasses more than writing requirements or managing a Product Backlog. Product Owners need to have a concrete understanding of all product management aspects, including but not limited to product ownership, that drives value from their products.

Read more

Martin Hinshelwood
🚀 Navigating the intricacies of the Sprint Goal in Scrum? 🎯 Discover the essence of crafting a goal that drives real value! 📈 Dive deep into the tactical steps, avoid common pitfalls, and ensure your team is on the right track. 🛤️ Let’s demystify the Sprint Goal together! 🤝 #Scrum …
Martin Hinshelwood
Software Development is not just a systematic process but a dynamic interplay of critical work that shapes the progress of your product. A Scrum team’s work can be classified into Sprint work and Refinement. To steer your Scrum Team towards success, it’s essential to understand, manage, and balance these two …
Daryn Basson Would you recommend the APS course to a newbie scrum team, and Why? Why the APS Course is a Must for Newbie Scrum Teams In this article, I’d like to share some thoughts on the Agile Practitioner Series (APS) course and its relevance to newbie Scrum teams. But first, …
Martin Hinshelwood
🚀 Navigating the nuances between the Definition of Done and Acceptance Criteria? 🤔 Dive into our latest article that explores the sanctity of a working, usable product without compromising value. 💡 Let’s ensure quality and value go hand in hand! 🤝


We believe that every company deserves high quality software delivered on a regular cadence that meets its customers needs. Our goal is to help you reduce your cycle time, improve your time to market, and minimise any organisational friction in achieving your goals.

naked Agility Limited is a professional company that offers training, coaching, mentoring, and facilitation to help people and teams evolve, integrate, and continuously improve.

We recognise the positive impact that a happy AND motivated workforce, that has purpose, has on client experience. We help change mindsets towards a people-first culture where everyone encourages others to learn and grow. The resulting divergent thinking leads to many different ideas and opportunities for the success of the organisation.