Requirements Prioritization

The requirement is critical to the project’s success. Without fulfilling this requirement, the project is not possible.

The requirement is high priority re the project’s success, but the project could still be implemented in a minimum viable product (MVP) scenario.

The requirement is important to the project’s success, as it provides value, but the project could still be implemented in an MVP scenario.

The requirement is low priority (i.e., it would be nice to have), but the project’s success is not dependent upon it.

The requirement is outside of the project’s scope and is included as a possible component of a prospective release and/or feature.