Nov. 16, 2011

Tips and Tricks for the beginner Product Owner: How long is your backlog?

It is not the size of your Product Backlog that matters!

Many Product Owners I coached are obsessed by the length of their Product Backlog. While the fact that I only encountered three female Product Owners in my whole career, might explain parts of this phenomena, there is more to explore about this.

A newbie Product Owner is often frightened about his backlog being too short. Having 15-20 User Stories ready for the next Sprint Planning is often hard for a beginner. After a while, it turns into an obsession, as a long Product Backlog gives a feeling of safety.

Guys, and the few Gals out there: It is not the size of your Product Backlog that matters! Keep three interesting numbers in your mind (from Dave Snowden):

5 - Number of things an average human can simultaneously keep in his mind

15 - Number of people a human being can trust

150 - Number of people we can keep as acquaintances (see Dunbar’s law)

You should be able to keep your backlog in your head. This is why it is not a good idea to let your backlog grow over 150 items at any given time. - If we cannot relate to more than 150 people, we cannot relate to 150 backlog items. Once it exceeds the 150 items limit, some of them are just going to be overlooked and this is worse than if they were not existing at all. Your relatives are going to be upset if you forget about them as well!

„Backlog Grooming“ does not mean to constantly slice all backlog items into little pieces. It does mean to keep the Product Backlog „detailed appropriately“ (see DEEP acronym). So keep your top requirements sliced into small pieces and wait with slicing the rest until it is their turn. Some items may never emerge to the top and will clutter your Product Backlog for a long time if you are not careful. It is a wrong assumption that anticipating work on low priority Backlog items will increase your efficiency , when it will be their turn to make it at the top of the backlog, they will have changed so much that you will have to start all over again.

Also, don‘t bother yourself or your stakeholders with low priority items. - And also don‘t bother your developers with estimations for those items, instead keep the Product Backlog as short as it can be. Consider having ready not more than the double of the items that normally get pulled out of the backlog for one sprint, more than that might be  waste.

Instead, focus on the top items and prepare the next Sprint. Part of the preparation for next Sprint is also the context, so be also ready to talk about the high level requirements for the next 3-4 Sprints and keep them high level.

Your backlog is your weapon for maximizing the return on investment and get your work done as well as transparently share what the defined order of execution is. Handle it with care and care for it often. It shall be detailed appropriately, the top items estimated, emergent and most important - ordered! (Meaning there is one priority 1 item and one priority 2 item and so on.) These attributes will be subjects of other blog posts in the future.

Keep it short enough to stay on top of it and long enough to allow your teams to chose which items to work on in the upcoming sprint.Remember also to provide enough context and direction about where the whole product is manoeuvring to. Its quality and not size that matters!

Image of fivancsich

Franz Ivancsich

blog comments powered by Disqus
Image of fivancsich

Franz Ivancsich

Latest Posts

Food for your soul: the FOODBOOM story

Passion for food and great ideas drove FOODBOOM and when the time came to confront their strategy and build on the vision they asked agile42 for help

Image of apanagiotou

Anna Panagiotou

Dive deep into Cynefin™ for Agile

Advanced Cynefin™ for Agile Masterclass with Dave Snowden in Berlin on September 24 and 25, 2019

Image of apanagiotou

Anna Panagiotou

From Agile to Agility in Lisbon

Andrea Tomasini will talk about ORGANIC agility and the path from Agile to Agility at the eXperience Agile conference in Lisbon on Sep. 30, 2019

Image of andreat

Andrea Tomasini

I am an Agile Coach and Trainer and I am helping customers all around the world to become more Agile. I am more and more keen on adopting adaptive emergent approaches to improve people's quality of life. Through an holistic and pragmatic approach - I consider Lean and Agile very powerful frameworks - it is possible to improve results, performance and also personal satisfaction.

Advanced Agile Team Coaching Course in Berlin and Helsinki

Join agile42 coaches to learn a more structured approach to coaching teams
Image of pascal

Pascal Papathemelis

Pascal has worked as an agile project manager/scrum master/facilitator of various developments in size and type for almost two decades. His focus is on people and practical approaches in order to deliver value. Currently Pascal is working at agile42 as an agile coach on a journey to help organisations and individuals grow, improve and become more efficient in a sustainable way.
Image of javierperez

Javier Pérez

Javier invested his first years of career working as developer and business analyst in Madrid. When Javier moved to Berlin, he discovered his passion: to help teams and organizations in their cultural transformation towards agility working first as Scrum Master and later as Team Coach.
Image of simsab

Simon Sablowski

Simon has spent several years working as a software developer, ScrumMaster and CTO. He is dedicated to shortening feedback loops to accelerate learning and strengthening team collaboration to maximise synergies. At agile42, Simon enjoys coaching and training teams and organisations that desire to attain higher productivity, continuous innovation and extraordinary performance.

Cynefin, Wardley Maps and ORGANIC agility in Stockholm

Workshop by Dave Snowden and Simon Wardley “Navigate uncertainty: Strategy and innovation with Cynefin™ & Wardley Maps” is coming to Stockholm

Image of sofia.svanback

Sofia Svanbäck

I am the Business Relationship Manager of agile42 in Finland and Sweden. I started working at agile42 in May 2018 and haven’t done anything so interesting before. The decision to join agile42 is a decision I am proud of today. My days are filled with customer related things, like negotiations, offers, and training / coaching bookings to mention a few.