Hello nrek-ga,
Congratulations on landing the interview! You are wise to do research
to be able to best present your qualifications for meeting the
requirements of the job. There are lots of resources available to help
you familiarize yourself with how to develop a Marketing Requirements
Document. I?ve collected a large selection of resources so that you
can gain a broad perspective on this topic. I?ve also included
resources for developing Product Requirements Documents and some
discussions on how MRDs are differentiated from PRDs.
Both Marketing and Product Requirements Documents refer to the reasons
for developing the product, descriptions for who will use the product
and how it will work and the specifics of how it will be built. Some
see the two terms as interchangeable or synonymous. Some see the MRD
as more strategic and the PRD as the more specific description of the
product.
I?ve provided lots of resources so that you can immerse yourself in
this topic in preparation for your interview. Although I wasn?t able
to find a sample MRD/PRD for an online consumer services company, I
have included several templates and samples that should give you a
good idea of what such a document should contain.
Please ask for clarification if any of this is confusing. I wish you
well for your interview and great success in your career.
~ czh ~
==================================================
MARKETING REQUIREMENTS DOCUMENT (MRD) -- TEMPLATES
==================================================
http://www.softwaremarketsolution.com/Files/Sample_MRD.doc
Sample Marketing Requirements Document
***** This is a 17-page template that gives you all the elements and
explains how you should prepare your own MRD.
---------------------------------------------------
http://www.myworktools.com/tp_cache/t4/tool_468.html
Marketing - Sample Marketing Requirements Document
Price: $3.99
At A Glance
This Word document is a template for writing a marketing requirements
document. It covers market needs, the customer value proposition, and
product functionality.
Background
Developing a marketing requirements plan is critical to your company's
long term success. To develop products that customers not only want
but will pay for is one of the most important strategic processes that
a company can undertake. This 'MRD' outlines the following key
elements: marketplace, target audience, users, constraints, naming
conventions, product boundaries, look and feel, usability, performance
and much more.
---------------------------------------------------
http://www.mironov.com/documents/toolset.html
Tools and Templates
Marketing Requirements Document (MRD) template
---------------------------------------------------
http://www.techtransform.com/process/PMTech/sampleMRD.pdf
Sample Marketing Requirements Document for Product X
=================================================
MARKETING REQUIREMENTS DOCUMENT (MRD) -- EXAMPLES
=================================================
http://completespm.com/mrd.pdf
Computer System Packaging: Marketing Requirements Document
---------------------------------------------------
http://www.trend.org/contest/mrd_1.htm
Market Requirements Document for ?File Sharing Community? version 1.0
---------------------------------------------------
http://home.earthlink.net/~lyttlec/documents/marketing/mrd.html
MARKETING REQUIREMENTS DOCUMENT FOR THE UNIVERSAL AUTOMOTIVE TEST SET
---------------------------------------------------
http://www.280group.com/samples/Software%20as%20Service%20MRD.pdf
Market Requirements Document
---------------------------------------------------
http://www.techtransform.com/process/PMTech/SUMMON12.pdf
Marketing Requirements Document SUMMONER
===========================================================
MARKETING REQUIREMENTS DOCUMENT (MRD) ? ARTICLES, RESOURCES
===========================================================
http://www.chanimal.com/Writing_the_MRD.pdf
Writing the Market Requirements Document ? April 2001
http://www.productmarketing.com/topics/01/04.htm
Writing the Market Requirements Document - Updated July, 2003
This document is written for product managers in high-tech companies
who are chartered with documenting product requirements in the form of
a Market Requirements Document (MRD).
-- Roles & Responsibilities
-- Definitions
-- Characteristics of a Good Requirement
-- Market Requirements in the Business Case
---------------------------------------------------
http://www.medrocket.com/tools/articles/article050201_01.html
10 Essential Elements for Your Online Marketing Plan
================================================
PRODUCT REQUIREMENTS DOCUMENT (PRD) -- TEMPLATES
================================================
http://completespm.com/product_specifications.html
Product Specification Document
---------------------------------------------------
http://fast.faa.gov/ams/reqdesc.htm
Requirements Document
---------------------------------------------------
http://www.ecst.csuchico.edu/ece/courses/ece210/twoPagSummaryChico.DOC
Hints for Writing Requirements
===============================================
PRODUCT REQUIREMENTS DOCUMENT (PRD) -- EXAMPLES
===============================================
http://www.oasis-open.org/committees/wsia/scenarios/wsia_business_scenario_product_configurator.pdf
Requirements Document
Business Scenario Report: Product Configurator Version 1.0
---------------------------------------------------
http://www.cc.gatech.edu/computing/classes/cs3302_99_summer/project/groups/Push42/requirements_document.html
Push42 Systems, Inc. -- Requirements Document
---------------------------------------------------
http://www.ligo.caltech.edu/docs/T/T950095-00.pdf
Vacuum Feedthrough and Cabling ? Design Requirements Document
=========================================================
PRODUCT REQUIREMENTS DOCUMENT (PRD) ? ARTICLES, RESOURCES
=========================================================
http://www.odegard.com/enews/aug2003/prd-delays.htm
Defining Product Requirements: How to Avoid Delays
In software product development, our primary tool for ensuring that
our product is what our customers need and expect is Requirements
Management. Unfortunately, gathering and documenting the requirements
often takes longer than we would like. In this article we will look
at six common sources of delay in defining product requirements, and
what can be done about them.
---------------------------------------------------
http://www.cooper.com/newsletters/2002_07/requirements_definition.htm
Bridging the gap with requirements definition
The PRD is where you actually define the requirements of the product.
The document itself can take many forms, but it should always include
compelling descriptions of why the product is being developed
(business and marketing goals), who will use it (personas and their
goals), what functionality is required of the product (persona needs),
and how it will be built (engineering goals).
---------------------------------------------------
http://www.amazon.com/exec/obidos/tg/detail/-/0201360462/104-1815252-4180750?v=glance
Mastering the Requirements Process
---------------------------------------------------
http://www.amazon.com/exec/obidos/tg/detail/-/1884777597/ref=pd_sim_books_3/104-1815252-4180750?v=glance&s=books
Practical Software Requirements: A Manual of Content and Style
---------------------------------------------------
http://www.wisdm.com/requirements.htm
The WISDM® Requirements Process uses an organization's own knowledge
and resources to quickly and efficiently create models of products and
services, business processes, and systems, models that are tailored to
the organization and its customers. Often, these models are called
requirements. In the WISDM process, requirements and a model of the
future are the same thing.
http://www.wisdm.com/requirements_document.htm
Each requirements document defines for whom the product, process or
application exists, what it must do, and how well it must perform.
Requirements do not specify how the product, process or application
will be carried out that is the role of the design process.
There is no universally accepted definition of what a requirements
document should contain or represent. Because of this, they vary from
simple lists of objectives and features to thousand-page
specifications.
====================================================
MRD OR PRD ? DEFINITIONS, ARTICLES, RESOURCES, TOOLS
====================================================
http://www.npd-solutions.com/pdef.html
PRODUCT DEFINITION
Comprehensive Specification
These customer needs then have to be translated into a set of product
requirements (more technical expressions of customer needs) that can
be acted upon by Engineering. Quality function deployment (QFD) is an
excellent methodology to support this objective while considering the
competitive situation. QFD is a structured planning and
decision-making methodology for capturing customer needs and
translating those requirements into product requirements, part
characteristics, process plans and quality/production plans through a
series of matrices.
These product requirements are often expressed in the form of a
product specification, functional specification, or marketing
requirements specification. The degree of formality in expressing
these requirements will vary depending on the complexity of the
product, the size of the development project, and the organization
structure and its communication requirements.
---------------------------------------------------
http://www.projectconnections.com/knowhow/template_list/
Templates & Checklists
Downloadable and editable project management templates and checklists
that you can put to use on your projects right away. Our templates for
project documents save you from re-inventing the wheel, and provide
you built-in best practices. Each project template has practical
guidelines and instructions for its use.
Concept Phase
-- Marketing Requirements Document
-- Product Definition - Success Factors
Initiation Phase
-- Product Requirements Specification
-- Software Requirements Specification
---------------------------------------------------
http://infrasystems.com/chapter3prodplan.html
Product Marketing Book -- Chapter 3
Product Conception
The Product Planning Process
Market Requirements Document (MRD)
Once the product planning process is complete and a product is
approved, you will need a Market Requirements Document. Some companies
call this the PRD or product Requirements Document. I call it a Market
Requirements Document because the most important point to focus on in
the document is what the market wants or needs. It also helps to
identify where the document is generated, in marketing.
---------------------------------------------------
http://www.maxwideman.com/pmglossary/PMG_P07.htm
Wideman Comparative Glossary of Project Management Terms v3.1
Product Requirements Document ("PRD")
A high level description of the product (system), its intended use,
and the set of features it provides. [D04750]
---------------------------------------------------
http://www.opus-plus.com/productsservices.html
Strategy and Business Case Definition
Product Definition
---------------------------------------------------
http://www-306.ibm.com/software/awdtools/reqpro/
IBM Rational® RequisitePro® is an easy-to-use requirements management solution.
http://www.eas.asu.edu/~cse461/CASEtool.ppt
What is RequisitePro
http://c2.com/cgi/wiki?RequisitePro
Requisite Pro
A truly hideous program for doing requirement specifications. Setting
up traceability is especially bad. Keeping people from doing this
awful repetitive work is why I got into programming.
===============
SEARCH STRATEGY
===============
marketing requirements document
sample marketing requirements document
template marketing requirements document
definition: marketing requirements document
product requirements document
sample product requirements document
template product requirements document
definition: product requirements document
MRD
PRD |
