Product Managers: The One Number You Should Know While Prioritizing Requirements »
By accompa on May 22, 2008 in Product Management | 2 Comments
A couple of excellent posts in the blogosphere this week emphasized why you should consider customer problems solved and value added to customers while deciding which requirements/features to implement in your next release.
Scott Sehlhorst wrote:
var addthis_pub = ‘accompa’;
var addthis_language = ‘en’;var addthis_options = ‘email, digg, delicious, reddit, linkedin, facebook, stumbleupon, more’;
