Roger asked some interesting questions on one of our previous posts about market and product requirements. In a couple recent articles, we presented some specific examples to clarify the semantics and language of different types of requirements. Roger asks six questions about functional and non-functional requirements in the comments on the last article. In this article, we answer them.
Product Management / Requirements
Posted on:
From Market Requirement To Product Requirements
We looked previously at an example of market analysis, defining first a market opportunity, and then a market requirement. We wrote an article a while ago about how to go from an MRD to a PRD. In this article, we will look at the journey from our market requirement to associated product requirements. And thanks, Roger, for throwing down the gauntlet.
Prioritization / Product Management / Requirements / Requirements gathering
Posted on:
Interrelation Digraphs As Prioritization Tool
Prioritization can be hard, especially when we’re dealing with a lot of variables. Peter Abilla, at shmula.com takes a fairly esoteric tool (interrelation digraphs) and applies it as a prioritization tool. Opthamologists have learned that they can’t show us a bunch of blurry images and have us tell them which one looks the best, and then prescribe a corrective lense. They have to ask us “Is it better like this? Or better like this?” Peter’s approach does the same thing, but with a quantitative edge.
Product Management / Project Management
Posted on:
Outside Reading and Thanks!
For your weekend reading pleasure, an interview and an article.
Product Management / Requirements
Posted on:
Market Requirement Valuation Example
OK, we’ve all read the theory about using value to identify market opportunities – can we see an example? Read on to see an example of creating a good market requirement.
Interaction design / Marketing / Product Management
Posted on:
How To Apply Market Research Better
Mike Mace provides us with some great insight about market research – helping us to avoid ‘the blender’ and ‘the gap’. The gap is a reflection of the inability of most customers to innovate. The blender is the loss of useful market information into a homogenized input that pushes only the lowest common denominator – again stifling innovation. We have to avoid the blender and the gap to get useful data from our research.
Business Analysis / Product Management / Requirements / Writing
Posted on:
Writing Correct Requirements
We ran a series called Writing Good Requirements – The Big Ten Rules in May 2006. Bloggers are notorious for not being able to count. We had ten rules at the time, and now we’re adding an eleventh. Writing Correct Requirements may have been the unwritten rule, but now we take a look at it.
Product Management
Posted on:
First Look at Free Market Product Management
Imagine if potential customers gathered together, each donating some funds, to specify the development of software. Those funds would be paid to whomever agreed to meet their demands. Essentially a free market system, balancing out supply and demand. Well, this has happened recently. Read on to take a first look at this and join in the discussion.
Product Management / Requirements
Posted on:
Does Your Product Have Soul?
Does your product have soul? Michael Shrivathsan asks this question, and we take it in a slightly different direction.