Priority Definition

on Tuesday, 01 January 2013. Posted in Business Analysis, Blog


A solution will be unable to fully address all the needs of all users 
Ranking and prioritizing each application requirement will allow the business to accurately evaluate and score each response
The following tables and outlines a possible framework you can use for your enterprise project for prioritizing the required application functionality:


‘Must have’
Functionality is a component of the current system capability
Functionality is critical to executing key business processes and procedures
Functionality is aligned with the business strategy
Functionality is necessary to execute on planned and in-progress initiatives
‘Nice to have’
Functionality would facilitate or support current business processes
Functionality may be incorporated into operations in the next 2-4 years
‘Future Potential Requirement’
Functionality is not required to execute current operations or near-term strategies
Functionality may or may not be incorporated into operations in the future



Copyright 2018 All rights reserved.