V 2.

Project Scope Example

Project Name Email Marketing System Project PROJ0321

Number
Project AT Napper Prioritization 1
Manager Melva
Russell Calhoun
Owner(s) Harry & David Start Date: 10/01/2009

Scheduled 03/01/2010
Completion
Date:

Mission The Purpose

Provide a Content Management System for Harry and David to disseminate email marketing offers to customers.
To provide Harry and David with an email marketing system to target customers with preferential emails, special
offers and discounts that are tailored to the customers past purchasing history and browsing.

Scope Clearly define the deliverables

• A Content Management System interface for the marketing department.

• Providing a network server where the software will be maintain and executed.
• Perform basic design of overall system
• Prepare details database design specifications for the order and browse history, product cross info, campaign,
and defined marketing segments layouts.
• Perform testing of system
• Perform installation of all subsystem at the Harry and David IT facility.

Harry and David

Page 1
 V 2.0

Define success criteria. If they are completed, the project mission will be accomplished.
Objectives Format: To + Action Verb + Measurable Output + Quantity + Time Frame

• To build an email marketing system that utilizes a Content Management system outlined in the system
development plans by March 2010.

Assumptions Clarify any uncertainties

• The network hardware and software will be available.

• A third party emailer package may be the best route for development
• The customer will be more receptive to emails that are customized for them instead of receiving random
mass emails from Harry and David.

Constraints Define limits placed on the project or project team

• This project must be completed by March 2010 to order for the system to ready for the spring national
marketing campaign. Delays will hinder the success of the campaign and potentially hurts sells.

Harry and David

Page 2
 V 2.0

Time/Decision Points Define key events which usually represent a significant deliverable. They may be
process indicators, decision gates, funding decision points or other significant
phases.

Activity Date
Requirements Gathering 10/01/2009
System Design 10/12/2009
Detail Design 11/2/2009
First Stage Release: Code & Test 11/9/2009
First Stage Release: System Test 12/14/2009
First Stage Release: Deploy 01/08/2010
Last Stage Release: Code & Test 02/01/2010
Last Stage Release: System Test 02/15/2010
Last Stage Release: Deploy 02/22/2010
Implementation 03/01/2010
Training 03/15/2010
Close Project 03/29/2010

Cost/Financial Assumptions Usually information from the feasibility analysis. Answers funding questions.

The Email Marketing System will cost approximately $300,000.

User Acceptance Criteria/Quality Basis for quantifying quality.

• The project team guarantees that all requirements will meet the marketing department needs by conducting periodic
stakeholder meetings that will require signature from the stakeholder to indicate the approval project requirements and
progression.

• Test scripts will be developed and provided to users for testing and approving all functionality provided by the system.
Acceptance of the functionality will require a signed document from the testing users and the business process owner.

Major Risks Define events which can affect the project’s success.

Internal Risks:
• In general, a major risk is getting behind schedule and missing the completion date
• Cost overruns can adversely impact the cost saving and revenue.
• Lack of stakeholder’s involvement in project
• Incompletely or inadequately defined market or customer needs and requirements
• Failure to identify newly introduced products/ systems by competitors.
• Costs come in under budget this can positively affect the release of the system and improve the ROI for system.

External Risks:
• Marketing conditions
• Government regulations pertaining to email dissemination
• Decisions by senior management regarding project priorities, staffing, or budgets
• Material or labor resources (shortages)
Harry and David
Page 3
 V 2.0

• Company’s need and behavior

• Competitors’ actions

Harry and David

Page 4
 V 2.0

KEY STAKEHOLDERS
Name
Project Core Team:
Melva Elliot
AT Napper
Russell Calhoun

Subject Matter
Experts (SME) Russell Calhoun
(Include company &
channel designations
if applicable)

APPROVALS
Type Name Signature Date
Project Manager Approval:

IT Project Manger @ H&D 09/10/2009

Owner/Sponsor Approval:

Marketing Department 09/10/2009

Harry and David

Page 5