Quote:
|
Originally Posted by gescober
How do you price the requirements? Based on development effort? risk?
|
I think the point is that you DON'T price the requirements; it's a market. The "price" is set by the willingness of the "buyers" to pay, not the cost to produce. In theory, the more of this perceived value you can deliver for any given amount of money, the happier the "buyers" will be.
It's not true in practice, but that's a general flaw with prioritization! Allow your project to be influenced by relative priorities, by all means. But stakeholders are no more likely to give you the correct priorities than they are to give you the correct requirements... Like any other assumptions, you have to continually re-verify as your plans become more concrete.