Evil Hacker Prioritization
New Product Owners often struggle with assigning a priority and business value to Product Backlog Items. A common refrain is “all my PBI’s are must-have! And they’re all maximum value!”
In a recent coaching session with one such Product Owner, we came up with a useful “thought experiment” for getting to clarity on this.
“Imagine it’s the day before release, and we discover that an evil hacker has broken into our system and installed ‘ransomware’ that disables a single Product Backlog Item. Which PBI would you choose?” The Product Owner thought for a moment, and picked one. He commented, “it’s sure a lot easier to decide what my lowest value feature is than my highest!”
We continued with the thought experiment. “Now, you receive a ransom demand from the evil hacker – if you pay it, the PBI you just chose will be unlocked. So what’s the most you’d pay to get it back?”
The Product Owner was unsure of the exact amount, so we grabbed a pack of Planning Poker cards and said, “One point equals a thousand dollars. Pick the card that is the highest amount you’d pay to get the feature back.”
The Product Owner picked a card, and we recorded this “ransom value “ in the Product Backlog.
We continued: “Unfortunately, the evil hacker rejects your offer, and out of anger, he disables another PBI. Which one would you choose next?” We repeated the cycle one by one, until there were no more PBI’s remaining.
It was very interesting to see how much easier the Product Owner found it to identify the lowest value item on the Product Backlog, and prioritize from the bottom to the top, rather than vice versa. And the “ransom” value turned out to be conceptually an easier way to zero in on the business value of each of the Product Backlog Items.
Current rating: 5 (5 ratings)
To leave a comment, please login with your scrumalliance.org credentials.