Product requirements document

(Redirected from Product Requirements Document) Outline of intended product functions

This article includes a list of references, related reading, or external links, but its sources remain unclear because it lacks inline citations. Please help improve this article by introducing more precise citations. (April 2016) (Learn how and when to remove this message)

Marketing
Management
Key concepts Distribution Pricing Retail Service Activation Brand licensing Brand management Co-creation Communications Consumer behaviour Consumer culture Dominance Effectiveness Ethics Promotion Segmentation Strategy Account-based marketing Digital marketing Product marketing Social marketing Influencer marketing Attribution Annoyance factor Horizontal integration Vertical integration
Promotional content Advertising Ambush marketing Branding Corporate anniversary Direct marketing Franchising Label Loyalty marketing Mobile marketing On-hold messaging Personal selling Premiums Prizes Product placement Propaganda Publicity Sales promotion Sex in advertising Underwriting spot
Promotional media Behavioral targeting Brand ambassador Display advertising Drip marketing In-game advertising Mobile advertising Native advertising New media Online advertising Out-of-home advertising Point of sale Product demonstration Promotional merchandise Promotional representative Visual merchandising Web banner Word-of-mouth
Research Market research Marketing research Mystery shopping Consumer research
v t e

A product requirements document (PRD) is a document containing all the requirements for a certain product. It is written to allow people to understand what a product should do. A PRD should, however, generally avoid anticipating or defining how the product will do it in order to later allow interface designers and engineers to use their expertise to provide the optimal solution to the requirements.

PRDs are most frequently written for software products, but they can be used for any type of product and also for services. Typically, a PRD is created from a user's point-of-view by a user/client or a company's marketing department (in the latter case it may also be called a Marketing Requirements Document (MRD)). The requirements are then analyzed by a (potential) maker/supplier from a more technical point of view, broken down and detailed in a Functional Specification (sometimes also called Technical Requirements Document).

Components

Typical components of a product requirements document (PRD) are:

Title & author information
Purpose and scope, from both a technical and business perspective
Stakeholder identification
Market assessment and target demographics
Product overview and use cases
Requirements, including
- functional requirements (e.g. what a product should do)
- usability requirements
- technical requirements (e.g. security, network, platform, integration, client)
- environmental requirements
- support requirements
- interaction requirements (e.g. how the product should work with other systems)
Assumptions
Constraints
Dependencies
High level workflow plans, timelines and milestones (more detail is defined through a project plan)
Evaluation plan and performance metrics

Not all PRDs have all of these components. In particular, PRDs for other types of products (manufactured goods, etc.) will eliminate the software-specific elements from the list above, and may add in additional elements that pertain to their domain, e.g. manufacturing requirements.

References

Categories:

Misplaced Pages