Link Details

Any project plan is a mixture of what the product owner wants and what the team can actually deliver. The product owner naturally wants more than the team can deliver, so s/he has to prioritize in order to get something useful in the desired timeframe. How do you convert an unordered list of features into a prioritized product backlog which you can give the team to implement? What should you do first? Let’s take a look at some widely used strategies for prioritizing the product backlog: Minimum Marketable Feature Set, Business Value First, Bang For Buck, Technical Risk First, Defer Risk, Vote