Framework to prioritize requirements

This is a simple model.

Assumptions

* It assume you can accurately determine the cost and value of each “feature”.
* It assumes the homogeneity of skills to perform these function.
* It assumes no interdependence of the requirements.
* It assumes requirements have been broken down consistently.

The framework provides a way to prioritize what gets build in the next iteration of the product.

The color scheme, indicates suggested order in which the requirements can be discussed
1. Blue
2. Green
3. Orange
4. Red.

The foot notes indicates some comments on the capacity, skills, process or platform related issues that this framework brings out.

*IF YOU ARE CONSISTENTLY PICKING ITEMS FROM THIS BUCKET, THEN YOU MIGHT HAVE TOO MUCH CAPACITY. IT MIGHT BE TIME TO RE-PURPOSE SOME PARTS OF THE TEAM.

** IF YOU ARE CONSISTENTLY UNABLE TO PICK REQUIREMENTS FROM THIS BUCKETS, IT MIGHT BE TIME TO EXTEND THE TEAM.

*** IF YOU ARE CONSISTENTLY UNABLE TO EXECUTE ITEMS FROM THESE BUCKETS, SOMETHING IS WRONG WITH TEAM SIZE, SKILLS PROCESS OR TECHNOLOGY PLATFORM.