‘Should have’ is for things that would be better to include, but you’re not destined for disaster without them. If you can’t picture success without it, it’s a Must have! Should have To work out if something qualifies as ‘Must have’ think about the worst and best-case scenarios for not including it. If it’s something that has been promised to your users and is a huge driver for the buzz around your upcoming release, it would be a terrible idea to launch without it. This could be for legal reasons, safety concerns, or business reasons. ‘Must have’ represents the features that you absolutely should not launch without. Let’s take a closer look at what these categories really mean: Must have The name is an acronym of four prioritization categories: Must have, Should have, Could have, and Won’t have. It’s a particularly useful tool for communicating to stakeholders what you’re working on and why. Known as the MoSCoW Prioritization Technique or MoSCoW Analysis, MoSCoW is a method commonly used in Agile PM to understand what’s important and what’s not. (PS Keep reading till the end for a special talk from Mariano Capezzani on The Art of Making Impossible Product Decisions.) 1. We’ll then show you some A* advice on the prioritization process of top product people. Here, we’ll show you the top three methods that all Product Managers should know MoSCow, RICE, and Kano. They’ve built great things, and built even greater prioritization frameworks! Luckily, a whole community of product experts have come before you. But for a successful launch, it has to be done. Choosing the high right priority can feel daunting. Prioritization is absolutely essential for product teams and to product development. Finally your Data Analyst is convinced that Feature B is completely unnecessary, and that users are crying out for Feature C. But a key stakeholder is gently suggesting that Feature B be included in V1. The engineers are telling you that Feature A will be really cool and will take you to the next level. In product, prioritization is on a whole other level! You’ve got a list of unprioritized features and tasks splayed out in front of you. You choose which task to work on first, which deadline needs to be met above all others, and what order to answer your emails in. If you’ve transitioned to product from another discipline, or have spent years working in any office-based role, you might already think you know how do it. One of the most challenging aspects of Product Management is prioritization.
0 Comments
Leave a Reply. |