PROJECT SCOPE STATEMENT

Note: Any work not explicitly included in the Project Scope Statement
is implicitly excluded rom the pro!ect"
Cre#te links to reerenced documents $e"%"& 'ink(To() * +y usin% Insert Hyperlink on your tool+#r"
Note th#t #ll documents th#t #re linked to the Scope St#tement +ecome p#rt o the Pro!ect
Scope #nd re,uire the s#me de%ree o m#n#%ement control" Such documents should +e
m#int#ined in # sep#r#te Scope directory #lon% with the Scope St#tement"
Pro!ect N#me:
Prep#red +y:
-#te $MM.--.////*:
0ersion 1istory $insert rows #s needed*:
0ersion -#te
$MM.--.////*
Comments
1.0
Page 1
2" Executi3e Summ#ry
Provide below a brief overview of this project (e.g., project purpose and justification):
Provide a brief project summary in the space below. his information may be
available in the Project !harter. "lso provide a lin# to the Project Charter for
reference.
'ink(To(Pro!ect(Ch#rter
Note: 4n #ny inst#nce where there is # discrep#ncy +etween the Project Charter #nd the Project Scope
Statement& the l#tter is considered #uthorit#ti3e"
5" 6usiness O+!ecti3es
5"2 Product -escription $Solution*:
5"5 6usiness O+!ecti3es:
7" Pro!ect -escription
For each area below, provide sufficient detail to define this project adequately:
7"2 Pro!ect Scope
4ncludes $list -eli3er#+les*:

-oes Not 4nclude:

7"5 Pro!ect Completion Criteri#:

7"7 Extern#l -ependencies:
7"8 Assumptions:
7"9 Constr#ints:
Page 2
8" Pro!ect Milestones
Estim#ted Schedules : 'ist key pro!ect milestones rel#ti3e to pro!ect st#rt" $4nsert rows #s needed*
Pro!ect Milestone T#r%et -#te
$MM.--.////*
Project $tart

Project !omplete
9" Pro!ect Appro#ch
9"2 Prim#ry Pl#ns ; <ill the pro!ect h#3e orm#l written pl#ns : i"e"& pro!ect schedule& +ud%et& ,u#lity& risk& etc"=
-escri+e +riely in the sp#ce +elow:
9"5 Scheduled St#tus Meetin%s $4nsert rows #s needed*:
Meetin% Purpose >re,uency
9"7 Scheduled St#tus Reports $4nsert rows #s needed*:
Report Purpose >re,uency
%riefly describe how each of the following will be handled. Provide lin#s to relevant documents as appropriate.
&odify e'ample te't provided or enter your own.
9"8 4ssue M#n#%ement: Project(related issues will be trac#ed, prioriti)ed, assigned, resolved,
and communicated in accordance with the Project Manageent
Methodology.
*ssues will be reported using an *ssue +eport ,orm. *ssue
descriptions, owners, resolution and status will be maintained in an
*ssues -og in a standard format.
*ssues will be addressed with the project owner and communicated in
the project wee#ly status report.
Page !
9" Pro!ect Appro#ch
9"9 Ch#n%e
M#n#%ement:
he change control procedures as documented in the .Project/ !hange
&anagement Plan will be consistent with the Project &anagement
&ethodology and consist of the following processes:
" !hange +e0uest -og will be established by the Project &anager
to trac# all changes associated with the project effort.
"ll !hange +e0uests submitted via !hange +e0uest ,orm will be
assessed to determine possible alternatives and costs.
!hange +e0uests will be reviewed and approved by the project
owner.
he effects of approved !hange +e0uests on the scope and
schedule of the project will be reflected in updates to the Project
Plan.
he !hange +e0uest -og will be updated to reflect current status
of !hange +e0uests.
9"? Communic#tion
M#n#%ement:
he following strategies have been established to promote effective
communication within and about this project. $pecific !ommunication
policies will be documented in the .Project/ !ommunication Plan.
he Project &anager will present project status to the project
$ponsors on a wee#ly basis1 however, ad hoc meetings will be
established at the Project &anager2s discretion as issues or change
control items arise.
he Project &anager will provide a written status report to the
project $ponsors on a monthly basis and distribute the Project
eam meeting minutes.
he project $ponsors will be notified via e(mail of all urgent issues.
*ssue notification will include time constraints, and impacts, which
will identify the urgency of the re0uest for service.
he Project eam will have wee#ly update3status meetings to
review completed tas#s and determine current wor# priorities.
&inutes will be produced from all meetings.
"ll electronic Project 4ocuments will be maintained in central
storage accessible by all project sta#eholders.
Page "
9" Pro!ect Appro#ch
9"@ Procurement
M#n#%ement:
" Procurement &anagement Plan will be written by the project team. *t
will document the following:
5ow much, when and by what means each of the goods and services
that this project re0uires will be obtained
he types of contracts re0uired (if any)
5ow independent estimates (as evaluation criteria) will be obtained
6ho will actually wor# to procure any item or service
6hich procurement documents will be used
5ow procurement will be coordinated with project schedule and
budget
6hat a $tatement of 6or# includes (e.g., how to describe a product or
service so that a prospective seller can decide if they can supply it)
" description of +,*, +,P, and other processes (if re0uired for the
project)
Potential sources of goods and services.
9"A Resource
M#n#%ement:
he project team will produce a +esource &anagement Plan that will
document the following:
-ists all major goods and services re0uired in the project along with
cost estimates and 0uality information.
*ndicates which goods and services will be obtained from sources
outside the 7rgani)ation
*ndicates who is assigned to the project and when.
?" AuthoriB#tions (Modify lists as needed)
The Scope St#tement& <6S& Pro!ect Schedule& Risk M#n#%ement Pl#n #nd Pro!ect 6ud%et #re
#ppro3ed +y the:
Pro!ect Sponsor
Pro!ect M#n#%er
Pro!ect perorm#nce +#seline ch#n%es will +e #ppro3ed +y the:
Pro!ect Sponsor
Pro!ect M#n#%er
Pro!ect deli3er#+les will +e #ppro3ed.#ccepted +y the:
Pro!ect Sponsor
Cey St#keholders
Page #
?" AuthoriB#tions (Modify lists as needed)
Speciic t#sk responsi+ilities o pro!ect resources will +e deined in the Responsibility
Assignment Matrix"
@" Pro!ect Scope St#tement Appro3#l . Si%n#tures
Pro!ect N#me:
Pro!ect M#n#%er:
$he purpose of this docuent is to provide a vehicle for docuenting the initial planning efforts for the project% &t is
used to reach a satisfactory level of utual agreeent aong the Project Manager, Project 'ponsors and (wners
with respect to the objectives and scope of the project before significant resources are coitted and e)penses
incurred%
I have reviee! the in"ormation containe! in this Pro!ect Scope St#tement an! agree:
N#me Role Si%n#ture -#te
$MM.--.////*
$he signatures above indicate an understanding of the purpose and content of this docuent by those
signing it% *y signing this docuent, they agree to this as the foral Project $cope $tatement docuent%
Page +