http://www.pragmaticmarketing.com daily 1 2007-06-02T15:10:00Z http://www.pragmaticmarketing.com/publications/topics/05/0501sk1 In my effort to build products with limited resources, I often spend time justifying the need for features. By Saeed Khan No publisher jlouie working with development requirements 2007-08-10T17:40:15Z Page http://www.pragmaticmarketing.com/publications/magazine/5/5/add-201cquick-hits201d-and-finally-address-those-priority-3-enhancements Woe to the minor enhancement request that gets tagged as a dreaded Priority 3 or nice-to-have feature during the prioritization phase of a project. All too often, it will get pushed into a future-release black hole—never to be seen again. By Chloe Morrow No publisher gjoyce product management working with development requirements 2007-11-06T14:54:20Z Page http://www.pragmaticmarketing.com/publications/magazine/4/3/ask “Our company seems to spend more time writing requirements and specifications than we do actually writing code and developing products. Shouldn’t we value the result more than the process?” No publisher jlouie pragmatic marketer requirements 2007-10-22T23:06:09Z Page http://www.pragmaticmarketing.com/publications/topics/09/before-the-market-requirements-document The market requirements document (MRD) is one of the key product management artifacts. But did you know there is a document that product managers should have in hand before they sit down to write a MRD? By Bob Corrigan No publisher graham product management requirements 2009-11-09T14:34:01Z Page http://www.pragmaticmarketing.com/publications/magazine/4/3/0605sk Delivering a successful beta program can be one of the hardest things to do as a product manager. By Saeed Khan. No publisher skhan product management working with development pragmatic marketer requirements 2007-08-10T18:25:26Z Page http://www.pragmaticmarketing.com/publications/topics/09/building-a-listening-post-online-for-customers Now, more than ever, companies are feeling the need to stay aligned with their customer’s evolving needs. By Sherri Dorfman No publisher ehannan product management requirements 2009-09-17T13:12:04Z Page http://www.pragmaticmarketing.com/publications/magazine/3/1/0501bh With 20,000 downloads of ProtectionPilot over a 10-week time span, McAfee received only 170 calls to support lines. Here are 23 detailed tips gleaned from McAfee and their external UI design team. By Bruce Hadley. No publisher bhadley working with development pragmatic marketer requirements 2007-06-17T18:45:04Z Page http://www.pragmaticmarketing.com/publications/magazine/8/2/conjoint-analysis-101 Know how your market values your product How do you know what the market wants? What market segments exist? What those segments prefer? What will they pay? In short, how do you know what trade-offs to make? By using conjoint analysis, understand the trade-offs you should make by understanding the trade-offs your market will make. By Brett Jarvis No publisher mconlon product management requirements 2010-08-10T22:50:03Z Page http://www.pragmaticmarketing.com/publications/topics/07/0702jm In most companies, Product Management is responsible for building, maintaining, and presenting the product roadmap inside and outside of the company. However, one of the biggest problems is they build, and build, and build, and finally re-build their roadmaps! By John Milburn No publisher jmilburn product management requirements 2007-08-14T04:08:10Z Page http://www.pragmaticmarketing.com/publications/topics/06/0604sj “My mom should be able to use it” translates into making an easy interface while “I want absolute control over the placement of items in my document” requires a powerful interface. By Steve Johnson No publisher sjohnson working with development requirements 2007-08-10T18:23:45Z Page http://www.pragmaticmarketing.com/publications/topics/02/0203sj Should we fix defects or add new features? Should we deliver on the promises we've already made to our customers, or should we make new promises to get new customers? By Steve Johnson No publisher jlouie working with development requirements 2007-08-10T17:21:09Z Page http://www.pragmaticmarketing.com/publications/magazine/5/3/easy-to-use-for-whom-defining-the-customer-and-user-experience-for-enterprise-software Enterprise software is only easy to use if the customer and user think it is easy to use. By Sean Van Tyne. No publisher svantyne working with development pragmatic marketer requirements 2007-07-02T16:32:07Z Page http://www.pragmaticmarketing.com/publications/topics/05/0511jm2 how Product Managers can play a vital role as the Requirements Police, making sure that important requirements are not forgotten. By Jacques Murphy No publisher jlouie working with development requirements 2007-08-15T19:35:03Z Page http://www.pragmaticmarketing.com/publications/topics/05/0501jm2 A major challenge that faces every software product is determining the priority of the oh- so-many suggestions that come to Product Management as requirements for the next release. By Jacques Murphy No publisher jlouie working with development requirements 2007-08-15T19:37:57Z Page http://www.pragmaticmarketing.com/publications/topics/01/0109sj In my seminars I often quote my rule that "he who owns the compiler wins." It's a reminder that product managers lack the political power to make developers do anything. Instead product management must persuade developers to build what the market will buy. By Steve Johnson No publisher sjohnson working with development requirements 2007-08-10T17:01:19Z Page