In this topic, we looked at a couple of different ways to prioritize your backlog. We used MoSCoW to judge value, and story points to estimate effort. And if you’ve noticed another theme of our work, it’s that we’re big fans of a matrix.

Just like we used grids for stakeholder analysis and risk mapping, you can apply the same thinking to backlog prioritization using a value vs effort matrix.

This short video from Relab Studios—How to Prioritize Your Product Backlog Like a Pro—walks you through a clear and practical way to plot your backlog based on how valuable each item is versus how much effort it will take. It’s great for spotting high-value, low-effort work—the kind of quick wins that Agile thrives on.

Want to take it further? You can assign a value score (using something like MoSCoW or your own scale), and divide it by the story points for effort. That gives you a rough priority score—great for when you’re trying to work out what’s worth squeezing into a sprint.

This technique is especially handy if you’re optimizing for velocity. When your team has limited time, this approach helps you choose the items that offer the best return on effort, keeping your sprints lean, focused, and delivering what matters most.