There’s a greater approach.
Product backlogs are inclined to develop in measurement sooner than the group can ship. The frequent situation: somebody comes up with an concept for a function, however you may’t deal with it proper now, so you set it within the backlog.
A couple of days later, another person comes up with a distinct concept, and the entire course of repeats. Once more, and once more, and once more.
Though it’s typically well-intended, placing each perception or concept within the backlog results in a set of issues.
First, it consumes lots of time. Including new objects to the backlog is simple, however managing them is a totally totally different story. Discovering outdated tickets, double-checking if one thing is already within the backlog, and linking dependencies can take days in outsized backlogs.
This complexity typically results in neglecting the backlog altogether. Objects get outdated, and other people don’t even keep in mind what the issue was anymore. In any case, it’s been sitting within the backlog for a 12 months, and quite a bit has modified since.
Outsized and thus uncared for backlogs are nowhere close to being the clear and respectable artefact they must be.
So, how can we keep away from an outsized concept backlog? By being selective about what we put there.
Every time there’s a brand new concept, perception or suggestion, there are three potentialities.
1. It is smart to plan it
Then plan it. Put it on the backlog, present it on the roadmap and begin getting ready for the execution.
2. It’s value exploring within the nearest time (1–5 months)
Put it in your discovery software. Ideally, it’s best to separate unsure concepts from issues you might be certain you need to ship within the foreseeable future. You could possibly use Alternative Answer Timber or their discovery artefacts to organise related insights.
3. It’s an ideal concept for the longer term
Burn it. And don’t look again.
The first purpose we find yourself with an outsized, unactionable backlog is the shortcoming to say no. Not solely to the stakeholders however to the concept itself. If the concept is promising, we simply don’t need to neglect it, so we put it within the backlog as a reminder. Throw the rock if the concept by no means crossed your thoughts.
However there’ll at all times be even cooler concepts. Even if you happen to reject an extremely promising concept at this time, you’ll have one other one tomorrow.
And if the concept is genuinely game-changing, then concern not. It can come again to you when you begin engaged on a associated goal.
