Daniel Hindi, BuildFireīugs should go into a triage and then get stacked and ranked based on their priority, impact, efforts, number of customers affected and how crucial it is. They are then forced to consider the business's needs over theirs. However, you can gather all stakeholders together with your current backlog of requests and ask them which request they'd like to see jump the line. If you're the gatekeeper of priorities, you are put in a position to constantly defend your choices. It all boils down to what will benefit the user the most. There are times when a feature request may not be addressed because, ultimately, we are looking at future capabilities that need to be factored in. Satisfaction could be defined in many ways, such as the speed to resolution, financial or even future feasibility. Let Customer Satisfaction Drive Your PrioritiesĬustomer satisfaction has to drive every decision. Using a prioritization matrix, you will be able to identify which features will make the most impact in relation to the necessity of the feature. You first need to define the product properly and outline the purpose, features and functionalities. You should have a clear understanding of the need or issue you are trying to solve so you can determine how you will address it. Susan Stone, Century Gaming Technologies The bug fixes are always a priority if it breaks a feature that your customers depend upon (reputation) or it breaks an accounting function (money). As far as new features go, they fall into the world of shiny things. There are always many amazingly good ideas but out of those ideas we choose those that will make us money or save us time - giving us a competitive advantage. Focus First On Issues That Impact Reputation Or Money Impact trumps ease of execution and limits tech debt in the process. For a product to evolve and meet the needs of your total (including potential) audience, it must stay true to the ultimate vision and guided, but not distracted, by disparate feature requests or bug fixes. The best products have a strong sense of purpose, molded by user data and feedback. It has to solve a specific business function.
![change priority matrix change priority matrix](http://mitsm-images.appspot.com/cdn/wiki/Change_Management_tables_category.gif)
#Change priority matrix software
For software to be effective, it can't be all things to all people. Even popular requests have to be looked at carefully. For requests, we wait to see how many requests for the same feature come in and then evaluate those that are popular. If something is not functioning as specified, it is a priority. Bugs get prioritized to get resolved, no question.