Product Backlog Defense – Common Patterns of Stakeholder Interference
Make no mistake: Your Product Backlog is the last line of defense preventing your Scrum Team from becoming a feature factory; hence Product Backlog defense is vital: Figure out a process that creates value for your customers. Moreover, have the courage — and the discipline — to defend it at all costs.
🗞 Shall I notify you about articles like this one? Awesome! You can sign up here for the ‘Food for Agile Thought’ newsletter and join 30,000-plus other subscribers.
The Product Backlog in the Context of the Product Creation Process
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 16 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 about 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 developers will think about how this product Increment will fit best into the application. However, the Scrum Team members’ discussion 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 six Sprints.
This transfer from product discovery to product delivery is a serious moment from the investment perspective. Now, the Scrum Team gets real and allocates resources to product delivery, for example, the continued collaborative refinement of the related Product Backlog items. Or sketches are turned into designs, and some preliminary work is probably required on the tech stack side. (Of course, this does not rule out that the Developers already contributed to final validation steps, for example, by creating a high-fidelity prototype with access to real-time data.)
Now the Scrum Team becomes accountable for spending money and producing a return on investment. Suppose you fail to deliver this return because you accepted some work that bypassed your team’s product creation process for whatever reason. In that case, you will be rightfully responsible for this failure, too. And no one will be interested in reading the fine print of why this happened. It is on you.
Product Backlog Defense: Expect Stakeholder Flanking Maneuvers to Bypass the Product Creation Process
Crossing the before-mentioned threshold is also 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 their 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.”
Join more than 100 peers from May 27-29, 2021, for the Virtual Agile Camp Berlin 2021, a live virtual Barcamp using open space technology principles and practices.
The Motivation Behind Flanking Maneuvers
There are various patterns of flanking maneuvers, depending on the organization’s nature, age, and size. For example:
- The case of the sales manager who believes their bonus is at risk and hence wants to throw some features urgently at the wall to see what sticks (and generates revenue) is evident.
- The case of someone who is pursuing a specific (pet-) project to improve their CV for the next career step – probably with another organization — is more challenging to spot.
- Often you can observe local optimization efforts by stakeholders valuing the results of their department higher than that of the whole organization.
- Then there is the drive to determine what the “internal software agency works on because it is our budget and we know our needs best.” Here, an organizational mindset — based on functional silos — of the industrial age clashes with the post-industrial value creation process.
Common Patterns of Stakeholder Interference with the Scrum Product Backlog
There are at least seven stakeholder interference patterns that make the Product Backlog defense mandatory for any Scrum Team:
- Pulling rank or HIPPO-ism: There are different reasons for this kind of behavior. Some people believe that hierarchical status has privileges and rules do not apply to them. Others think that they know best, probably fueled by a paternalistic mindset. Often, it is a sign of a lack of trust in the team’s capability. No matter what makes an individual behave this way, it is a sign of poor leadership qualities. (Quote.)
- Brute-forcing it: The bully at work, now probably plowing through a corporate hierarchy. What worked in the school-yard might still work today — differently packaged, though. Don’t expect this behavior to leave a trail of artifacts or email threads.
- Have daddy fix it: The magic of outsourcing the solution of ‘issues’ — here: the Scrum Team asks the stakeholder to accept the process like everyone else — to a higher hierarchy level. (‘My boss will talk to your boss, and then we will see…’)
- Bribery: I scratch your back, you scratch mine.
- Direct ticket creation: Why bother the Product Owner? They might be overworked anyway. Instead, your stakeholder shows initiative and creates the ticket for the required feature themselves. (Not controlling access rights to the ticket system is a rookie mistake, just saying.)
- Dispatcher mode: Why not assign a task directly to an engineer bypassing the Product Backlog altogether?
- Labeling feature requests as bugs: By comparison to the other maneuvers sneaking features via bug reports is almost a thoughtful approach — someone tries to hack the system. Nice try. Try harder next time, though.
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, please do not use the Product Backlog as a repository of ideas that might only be useful later, thus clogging it, muddying the signal in a lot of noise. Apply these rules indiscriminately to everyone.
Conclusion – Product Backlog Defense
If you want to be taken seriously as a product team and want the organization to accept your Scrum 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.
✋ Do Not Miss Out and Learn about Product Backlog Defense: Join the 9,000-plus Strong ‘Hands-on Agile’ Slack Team
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’s free.
Product Backlog Defense — Related Articles