Page 6
1. Introduction
<< A PRD describes a proposed product (and its features and benefits)
in terms of its business / market / customer requirements. It is created
by a Product Manager / Product Marketing Manager, and used by
Engineering as input for downstream analysis and design activities.
The document also prescribes tentative build / release schedules which
can be used by engineering, QA (Quality Assurance), Corporate
Marketing, and Professional Services to plan their release / go to
market efforts. >>
(Note: The document should be reviewed and approved by the executive
management as appropriate: CEO / CTO / CIO / VP – Marketing / VP – Sales /
VP –Product Management. Other managers whose inputs should be considered
include VP – Hardware Engineering, VP – Software Engineering. The PRD must
also be reviewed and approved by some / all of these departments: Quality
Assurance, Manufacturing, Compliance, and Customer Support. Depending on
where the product / product line fits into the strategy of the company / business,
other departments like Corporate Marketing and Corporate Finance may also
like to get involved with the product; consequently their inputs should be taken
into account, documented in short in the document revision trail, and weaved into
the overall PRD…)
1.1 Product Description
<<The product snapshot / description can go here. As such, multiple
ways to describe a product exist. One approach to target the product at
the intended customer segments can be to describe the jobs the
customers will be able to do better / cheaper / faster if they used the
©2007 - 2009 Franteractive Inc. All rights reserved.
