One gigantic missing component is a time estimation. A short time estimate on an important feature could change something from "should have" to "must have". How

One gigantic missing component is a time estimation. A short time estimate on an important feature could change something from "should have" to "must have". However, estimating time for development projects can get be difficult. This is why Atlassian pushes the idea of "story points", which is a rough estimate of complexity without real units. This works okay, but you need to have some kind of basis for story points. We went with (using the fibonacci sequence): - 1 - half a day or less - 2 - about a day - 3 - more than a day, less than 2 - 5 - 2-3 days - 8 - about a week - 13 - more than a week, probably less than 2 Etc. This gives our business types something they understand, while providing enough flexibility that developers feel comfortable. Business types need to know the scale of a project as well as its importance, since those two are very much connected.