How do you prioritize features for development?

Question

Our team has been using different estimation tactics. We have been trying to research and test some ideas before starting development. But no matter what we are doing, we always have an overwhelming amount of "critical" functionality that needs to be done before the next release or pivot.

How do you find what features to focus on or what functionality is possible to eliminate?

Yurii Holovanov · Accepted Answer

Ask your users. They definitely know in mass what they want to see first. What is critical for you might be just "meh" for them.

Gurkaran Singh · Answer

Ah, juggling critical features feels like playing whack-a-mole sometimes, doesn't it? Prioritizing can be as tricky as picking a favorite ice cream flavor - tempting but requires a balanced decision. Maybe it's time for a feature bake-off to see which ones rise to the occasion!

Teddy Atkins · Answer

“Critical” product feature prioritization should align with the company’s objectives. For example, if the immediate company objective is growth, resources should prioritize “critical” features that will support company or user growth over value or retention focused features.

Artem Bukharin · Answer

Using the RICE model. It's the simplest way

How do you prioritize features for development?

Replies