Professional Scrum Trainer (PST) with Scrum.org.
Product backlog defense — make no mistake: Your product backlog is the last line of defense preventing your team from becoming a feature factory. Figure out a process that creates value for your customers. Moreover, have the courage — and the discipline — to defend it at all costs.
In my keep-it-simple and thus two-dimensional product world, the product backlog defines the near-term planning as the lynchpin of the product creation process:
The near-term planning horizon in my mental model covers about four to eight weeks. It is where the product discovery phase delivers validated ideas of valuable product increments to the product delivery phase. (I shy away from calling it a hand-over as this term has a negative connotation rightfully.)
At this moment, there should be no longer doubts why a product increment is valuable to your customer and your organization — the ‘why’ question has been answered at this stage. Probably, you will still discuss the scope of the idea for its first delivery, and the engineers will think about how this product increment will fit best into the application. However, the discussion among the team members should no longer revolve around basic questions from the ‘valuable, feasible, usable’ perspective. That has been accomplished further to the left side during the product discovery phase.
If you are practicing scrum, the near-term planning will cover something between two to four sprints:
This transfer from product discovery to product delivery is a serious moment from the investment perspective. Now, the team gets real and allocates resources to product delivery, for example, the continued collaborative refinement of the related user story. Or sketches are turned into designs, and probably some preliminary work is required on the tech stack side.
Now the team becomes accountable for spending money and producing a return on investment. If you fail to deliver this return because you accepted some work that bypassed our team’s product creation process for whatever reason you will be rightfully accountable for this failure, too. And no one will be interested in reading the fine print why this happened. It is on you.
Crossing the before-mentioned threshold is also the reason why the near-term planning or the product backlog part of the product creation process is so attractive to stakeholders who try to bypass the process and sneak in requirements or features.
Entering a competition of ideas and hoping that an idea will pass validation is a considerable effort and bears a significant risk of being rejected. The shortcut of targeting the near-term planning phase instead is hence less risky.
Typically, you can attribute a stakeholder’s attempt to evade the competition of ideas part of the product discovery phase to his or her incentives provided by the organization. Or as Charlie Munger puts it:
“Never, ever, think about something else when you should be thinking about the power of incentives.”
The latest, 219 pages strong version of “Agile Transition — A Hands-on Manual from the Trenches w/ Checklists” is available right here, and it is free!
There are various patterns of flanking maneuvers, depending on the nature, age, and the size of the organization. For example:
If you prefer a notification by email, please sign-up for my weekly newsletter and join 16,261 peers.
There are at least seven flanking maneuvers that make the product backlog defense mandatory for any product team:
A note of caution: Do not outflank yourself during product backlog defense. The discipline to defend your product creation process from stakeholders’ attempts to bypass it needs to be applied with the same rigor within your team. For example, do not use the product backlog as a repository of ideas and requirements that might be useful at a later stage. Apply the same rules indiscriminately to everyone.
If you want to be taken seriously as a product team and if you want the organization to accept your product team as the go-to team that solves critical customer problems and identifies opportunities for the organization then defend your process with tooth and claw. Making exceptions from this rule is a slippery slope leading to becoming a feature factory.
Download your invitations:
Note: All webinars are aired from 06:00 to 07:00 PM CEST. (That is 12:00 to 01:00 PM EDT or 09:00 to 10:00 AM PDT.)
I invite you to join the “Hands-on Agile” Slack team and enjoy the benefits of a fast-growing, vibrant community of agile practitioners from around the world.
If you like to join now all you have to do now is provide your credentials via this Google form, and I will sign you up. By the way, it is free.
Product Backlog Defense was first published on Age-of-Product.
Level up your reading game by joining Hacker Noon now!