MicroSurvey Mobile Priorities

Prioritizing defects and features based on the following resources as a guide:

• Prioritizing Defects - https://michaellant.com/2010/05/25/a-simple-agile-defect-management-process/
• Prioritizing Features - https://michaellant.com/2010/05/21/how-to-easily-prioritize-your-agile-stories/

The priority rank is calculated as shown below:

Defect Ranking	Feature Ranking

Scope	Guidelines	Business Value	Guidelines
5	Affects most or all users and/or a very large range of system functionality	5	Extremely Important to most or all customers Extreme impact on brand or reputation Critical to the success of the business
4	Affects a large set of users and/or large range of system functionality	4	Important to many customers Significant impact on brand or reputation Significant competitive advantage
3	Affects a moderate set of users and/or moderate range of system functionality	3	Important to a moderate number of customers Moderate significant impact on brand or reputation Moderate important competitive advantage
2	Affects a small set of users and/or a small range of system functionality	2	Important to only few customers Minor impact on brand or reputation Minor competitive advantage
1	Affects a minimal set of users and/or a very small range of system functionality	1	Important to only a few or even no customers Little or no impact on brand or reputation Little or no competitive advantage

 

Severity	Guidelines	Urgency	Guidelines
5	Data loss, data corruption or system unavailable	5	Extremely time constrained Extreme level of dependency of other items on the completion of this task If not completed immediately there is little or no value to doing it
4	Important functionality is unavailable with no workaround	4	Highly time constrained High level of dependency of other items on the completion of this task Important to go into the next sprint because of customer or contractual requirements
3	Important functionality is unavailable but has a reasonable workaround	3	Moderately time constrained Moderate dependency of other items on the completion of this task Desirable to complete in the next one or two sprints
2	Secondary functionality is unavailable but has a reasonable workaround	2	Minimally time constrained Minimal dependency of other items on the completion of this task Completion in the next two or three sprints is adequate
1	Cosmetic issues or some functionality unavailable but has a simple workaround	1	Not time constrained No dependencies Little or no impact