MRD Mini-FAQ
Gabriel Steinhardt
Founder, Author, Public Speaker. Developer of the Blackblot Product Manager's Toolkit? (PMTK) Methodology
Answers to common questions on the Market Requirements Document?(MRD).
The Market Requirements Document (MRD) is one of the most critical deliverables in product management.
The following MRD Mini-FAQ (Frequently Asked Questions) answers common questions on the topic of the MRD.
What does MRD stand?for?
MRD means Market Requirements Document.
Is the MRD a process or a deliverable?
The MRD in itself is not a process; it is a deliverable.
The MRD is the main deliverable and output of the Product Planning process.
Which corporate department has ownership and responsibility for the?MRD?
The Product Management department owns the MRD.
Specifically, the MRD is separate from the Marketing or Engineering departments.
Who writes/prepares the?MRD?
?The Product Planner (aka Product Manager) writes/prepares the MRD.
Which process is used to gather information in the preparation of an?MRD?
The Voice of the Customer (VOC) is a process used to elicit customer needs.
The VOC is a sub-process within the Product Planning process.
What type of information does the MRD?convey?
?The MRD expresses the market problem in a way that allows product developers to offer a solution.
How does the MRD express the Market?Problem?
?The MRD manifests a methodology of expressing users’ needs.
The most common methodology used in an MRD to express user needs is Market Requirements.
Developed by Blackblot, the Blackblot Procedural Requirements Management? Model (PRM Model) is a methodology to create high-quality, usable market and product requirements.
Do user, customer, business, or marketing requirements mean the same as market requirements?
No, they are all different types of requirements.
Market requirements are the only type of requirements in an MRD.
What is a market requirement?
A market requirement is an aggregate unit of information that sufficiently details the functionality sought to address a specific facet of a particular market problem.
Do market requirements describe the product’s features, physical attributes, or technology??
No, market requirements do describe the product features or technology.
领英推荐
Do market requirements change when the solution?changes?
Market requirements do not change or expire when the technology or the solution evolves.
For the most part, market requirements stand the test of time, and how they are written fundamentally does not change over time.
Is the MRD used only to develop software or technology products?
The MRD is not a tool explicitly confined to software development or any technology product.
The MRD and the methodology for preparing market requirements can be used to plan any type of business or consumer product or service.
What information is contained in the?MRD?
The MRD describes the market opportunity, market problem, and the resulting market requirements.
The most significant component of the MRD is the market requirements, which detail the functionality sought by the collective users to address their market problem.
Does the MRD contain any marketing, business, or product information?
The MRD does not contain assessments and information from a Product Requirements Document (PRD), Business Case, or Market Plan.
Is the MRD a rigid document used only in a Waterfall approach to software development?
No. The MRD can embody a rigidity or agility mindset, regardless of the product type and the software development method employed by the product development team.
In the product delivery process, what subsequent deliverable follows the?MRD?
The Product Requirements Document (PRD).
What is a PRD, and what does the PRD?express?
The PRD is a high-level description of the solution, its intended use, and the set of features the solution provides that address the market problem and satisfy needs.
How does the PRD express the solution?
Like the MRD, the PRD manifests a methodology for expressing product features.
The most common methodology used in the PRD to express product features is Product Requirements.
Who writes the?PRD?
The Product Architect writes the PRD.
The Product Architect title is commonly synonymous with solution architect, solution engineer, business analyst, systems analyst, requirements engineer, requirements manager, and product designer.
Must a PRD follow the?MRD?
The MRD is a tool in Product Management (problem space).
When dealing with software development, the developers in Engineering (solution space) can use a PRD, product backlog, or anything else they want and work according to any software development method.
However, choices in the solution space are independent of the MRD or product management practices.
For details information, see the Extended Review of Market and Product Requirements.
Learn More…
Blackblot is the developer of the PMTK? methodology and the premier provider of private training, certification, tools, and expert services for market leaders and innovators worldwide. Blackblot is an IS0 9001:2008 certified business.