Nobody knows the product better than the team who built it. However, if you built an app that read minds (a stretch we know) it would take a lot longer than a few days to build and involve a lot more effort, but there certainly wouldn’t be another on the market. Throwing together a social media app might take the least time, but there are already a lot of really great ones out there, and pretty much anyone with the knowledge can build one, which makes the market risk high. If you can’t accurately estimate profit, you have to estimate the market risk. It’s important you weigh up a feature’s risk and how likely it is to put a strain on the development team, the business’s bank account, and the estimated time frame. We all know problems can arise in the development phase, delays, technical hitches, added costs. This sort of forward-thinking can save you a world of pain in terms of bugs, delays, and technical issues in the final stages, with little to no team members available to help. However, if it’s just too expensive to build right now, it may not be worth the effort (even if it’s set to make a handsome profit).ĭo you have the time? The availability? The numbers to make this feature happen? You might have a feature that you’ve estimated will take around 10 weeks to complete, but Christmas is around the corner, will you still have the same amount of manpower then? If the answer is no, focus on the feature that takes half the amount of time. How much will it cost to build this feature? If the estimated profit is set to be huge and the cost is low by all means carry on. Don’t lose sight of the bigger picture or the most attractive profit margin. Will this feature make a profit? How much will it cost to build vs how much profit will it yield? Sounds obvious, we know, but the initial reaction to focus on the feature which costs the least to build isn’t always the right one. When you’re deciding which features to prioritize there’s a lot to weigh up, are you looking for a short term win right now or working towards long-term growth? How do you give the input and ideas from developers, stakeholders, sales, and the rest of the product team the consideration they deserve? Take a look at the following:
#Change request priority matrix how to
We’ll talk you through the points you’ll need to consider when prioritizing requests, and how to prioritize them using popular frameworks. Which is why we’ve put together this guide!
Prioritizing feature requests is an ongoing process for product teams, you have to work together to consider the cost of the requests, market competition, and available resources as well as considering the business objectives, it can be a tricky balancing act. But how do we decide which of these features to focus on first or at all? Let’s face it, building new features is one of the most exciting aspects of product marketing, smashing customer expectations and consistently improving a product for users is the reason we do what we do.
0 kommentar(er)
