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:
You won’t go wrong by focusing your company, your strategy, and your products on solving valuable problems.
Jeff Lash said:
Rather than simply […]
