Download MS-Word`97 PDR template document

CERN
European Laboratory for Particle Physics
<PROJECT NAME>
Project Definition Report
<An Opportunity to …>
Authors :
Version :
Source : <MS Word'97, …>
CERN Note
READERSHIP ....................................................................................................................................................... 3
OBJECTIVES OF THE PDR .............................................................................................................................. 3
MANAGEMENT SUMMARY ........................................................................................................................... 4
PROJECT CONTEXT.......................................................................................................................................... 4
PROJECT PURPOSE AND BENEFITS ........................................................................................................... 5
PURPOSE ............................................................................................................................................................... 5
PROJECT SCOPE AND CONSTRAINTS ....................................................................................................... 5
SCOPE .................................................................................................................................................................... 5
CONSTRAINTS ....................................................................................................................................................... 5
PROJECT OBJECTIVES.................................................................................................................................... 5
PROJECT MODEL .............................................................................................................................................. 6
PROJECT MILESTONE PLAN ........................................................................................................................ 7
ORGANIZATIONAL STRUCTURE ................................................................................................................ 8
ORGANIZATIONAL BOUNDARIES AND INTERFACES ........................................................................ 8
MONITORING AND CONTROLLING MECHANISMS ............................................................................ 9
RISK ANALYSIS................................................................................................................................................... 9
REFERENCES ..................................................................................................................................................... 11
2
Chapter
1
Preface
Readership and Objectives of this document
Readership
<State the people (individuals or people belonging to specific organisational units) who
are supposed to read this project definition report.>
Objectives of the PDR
<State the objective(s) of the PRESENT DOCUMENT (not of the project !) and try to
link the objectives to the different categories of people enumerated in the Readership
section>
3
Chapter
2
Project Background
Management Summary and Project Context
Management Summary
<Record here the different managerial steps (i.e. memorandums, decisions, …) which
have led to the start of the present project>
Project Context
<Explain the context in which the project will start. This should include : previous
projects aimed at solving the same problem, on-going projects which will have to
interface with this project, working cultures or aspects which may influence directly
or indirectly the future of this project. Do not explain in too many details how
interfaces with other projects will be handled, this particular aspect is addressed
later in a specific section about interfaces>
4
Chapter
3
Project Definition
Project Purpose, Scope and Objectives
Project Purpose and Benefits
Purpose
<State in a very clear and non ambiguous way what is the purpose of this project. This
should answer the question: "Why do we do this project? What are the problems to
be solved? Is there an opportunity for improvement? What will be the benefits for the
organisation? >
Project Scope and Constraints
Scope
<State the different areas of work that will fall under the responsibility of this project (i.e
software development, production of specification, transfer in operation, …)>
This section must answer the question: How much work is involved in this project?
>
Constraints
<State the different constraints which will limit the number of possible choices in this
project (i..e limited resources, responsibility limitations, constraints on technical
choices, compatibility issues, …)>
Project Objectives
<State the main objective(s) or results to achieve in the scope of this project.
These objectives MUST be clear and measurable. They will serve and be part of
the future project milestone plan.
This section must answer the question: What will this project deliver ? >
5
Chapter
4
Project Model and Milestone Plan
Project Model
<Explain the process model that will be used in this project. This may contain a
description of the different phases that will take place with their inputs and outputs.It is
highly recommended to use a combination of textual and graphical notations.
Just an example of project model :
CERN PS/SL Controls Infrastructure Convergence Model
K.Hubner Memorandum
11/12/1996
K.H.Kissler, D.J.Simon
Memorandum 1/8/1997
Audit and Exploration
Phase
Audit Report
B.Frammery, R.J.Lauckner
Mandate March, 1998
Project
Def inition Phase
Project Def inition Report
Convergence Implementation Phase
Long te rm Im ple m e ntation
Strategic Planning
Short te rm Im ple m e ntation
Activities and/or sub-projects
3
Java API
sub-project
sub-project
2
Control System Building blocks
Common PS and SL Controls Inf rastructure
Fig.1 CERN PS/SL Convergence Project Model
6
4
Project Milestone Plan
The strategic milestone plan outlines the major intermediate managerial and technical
results (milestones) to be achieved to reach the final objective of the project
MILESTONE PLAN - Long Term Strategy
Project: C ERN PS/ SL C ontrols
Sub
Hig h
C onverg enc e
Projec t Ma na g
Ma na g
Planned date
S
H
2/ 28/ 98
H1
3/ 5/ 98
H2
3/ 10/ 98
H3
S1
Milestone
When PS/ SL Softw a re infra struc ture C onverg enc e Projec t Definition Rep ort is rea d y and va lid a ted b y the PS a nd SL a uthorities
a uthorities
g
roup sthe
leasc
d ers
When
ena rio for la unc hing , a nd / or tra c king a c tivities rela ted to ea c h c ontrol system d elivera b le is d efined
(ma
a tory
d efinition of sc op e, p riority, resourc es, milestone a nd ma intena nc e p la ns, 1st
a nd nd
p ub
lished
imp
lementa
e) oing a nd future projec ts a nd their IN/ OUT d elivera b les a re id entified a nd d oc umented a nd
When
a ll PS ation
nd sc
SLop
on-g
req
-p rojec ts or a c tivities to sta rt is rea d y (linked to p rec ise d elivera b les) for a p eriod
a p uired
riority sub
list of
of
6 months
When
a c tivities rela ted to a g iven c ontrol system d elivera b le a re launc hed follow ing the sc ena rio
d efined in H2.
When the tea m in c ha rg e of a g iven c ontrol system d elivera b le ha s p rovid ed a p rojec t d efinition rep ort inc lud ing high
a
c c ord
ing to the sc ena rio d efined in H2 and w hen this p rop osa l ha s b een va lid ated b y the
level
milestone
cWhen
onverg
enc
em
tea
the
tea
inmc ha rg e of a g iven c ontrol system d elivera b le ha s p rovid ed a d elivera b le ma intena nc e a nd sup p ort
S2
S3
to
rio d efined in H2 a nd w hen this p rop osa l ha s b een va lid a ted by the
p lathe
n a sc
c cena
ord ing
cWhen
onverg
enc
e tea
m system d elivera b le is d ec la red rea d y b y the tea m
a g
iven
c ontrol
S4
resp onsib le for it
When a g iven c ontrol system d elivera b le is va lid a ted by the c onverg enc e tea m (vs the imp lementa tion d efined in
cS2)
ommon
PSin
a nd
a nd p ut
theSL softw a re
rep
ository
When
a review of the 6 months p eriod is ma d e a nd future a c tions a re d ec id ed (re-sta rt from a new
S5
H4
H3 for exa mp le)
H5
When PS a nd SL a uthorities a g ree tha t a c ommon c ontrols infra c truc ture is in p la c e a nd d ec ision is ta ken reg a rd ing
the
future
of this
p
rojec
t
2/24/98, Page 1
7
Chapter
5
Project Organization
Organizational Structure, Organizational boundaries and
Interfaces
Organizational Structure
<Describe the internal management structure of the project. Graphical devices as
hierarchical organisation charts or matrix diagrams may be used to depict the lines of
authority, responsibility and communication WITHIN the project.>
Organizational Boundaries and Interfaces
<Describe the managerial and administrative boundaries between the project and
each of the following entities : the parent organisation, the clients or users,
subcontracted organisations, external and/or sub-projects, or any other organizational
entities that interact with the project.
In addition, administrative and managerial interfaces of the project support functions,
such as configuration management, quality assurance, and verification and validation
(by CERN operation groups for example) shall be specified in this section.>
8
Chapter
6
Managerial Process
Monitoring and Controlling Mechanisms, Risk Analysis
Monitoring and Controlling Mechanisms
<Explain the managerial monitoring and controlling mechanisms (philosophy) that will
be used. This could for example contain the production of milestone plans,
responsibility charts and progress reports compliant with the Goal Directed Project
Management (GDPM) approach, the way budgets will be defined and resources will
be allocated>
Risk Analysis
<Identify and assess the risk factors associated with the project. This includes
contractual risks, technological risks, risks due to the size and complexity of the
project. Say also how the project will try to minimise these risks.>
9
Chapter
7
Technical Process
Methods, tools and techniques
<State which formal methods (i.e. OO modelling tool, software development
environments) will be used in the different areas of work. This may include a
description of the desktop tools that will be used to produce and distribute
documentation (i.e. MS-Word and WWW, which project management software will be
used (for planning, resources allocation, …) and so forth>
10
References
<State all documents used to build this milestone plan and documents related to specific tools
and/or techniques used in this project>
11