ProductDescription, Prince2 Document Templates And Examples

[ Pobierz całość w formacie PDF ]
SPOCETTE - Managing Minor Projects - Project Kick-off Template
STANDARD PRODUCT DESCRIPTIONS
SPECIALIST PRODUCTS
The following Specialist Product Descriptions have been prepared as useful starting-points
for most projects under the control of the SPOCE-Extra Method. They should always be
evaluated for relevance and suitability by the Project Manager when preparing the Project
Initiation Document (PID 0, 1 and 2). Changes should be recorded and notified to the
Programme Support Office who will issue and amend the standard list from time to time.
Where new or different Specialist Product Descriptions are produced, the Project Manager
must copy the new Product Descriptions to the Programme Support Office, who maintain
copies of suites and individual Product Descriptions for use by other projects.
Before preparing new Product Descriptions it is worth checking with the Programme
Support Office to see if they already hold similar material.
STANDARD SPECIALIST PRODUCTS
D.1.0
- User Requirements Specification
Appendix C1
D.2.0
- Overview Of Requirements
Appendix C2
D.3.0
- Design Specification
Appendix C3
D.4.0
- Developed End Product
Appendix C4
D.5.0
- Validation And Acceptance
Appendix C5
D.6.0
- Business Process Definition
Appendix C6
D.7.0
- Implementation Plan
Appendix C7
D.8.0
- Product Evaluation
Appendix C8
D.9.0
- Product Enhancements
Appendix C9
D.10.0
- Equipment/Infrastructure Requirements
Appendix C10
D.11.0
- Data Cleanse/Conversion
Appendix C11
D.12.0
- Go Live Plan
Appendix C12
D.13.0
- Go Live Acceptance & Handover
Appendix C13
D.14.0
- Training Plan
Appendix C14
D.15.0
- Post Implementation Review
Appendix C15
1
SPOCE Project Management Limited - HO0103 v.1
 SPOCETTE - Managing Minor Projects - Project Kick-off Template
APPENDIX C1
SPECIALIST PRODUCT DESCRIPTION
REFERENCE D.1.0 - USER REQUIREMENTS SPECIFICATION
PURPOSE/DESCRIPTION:
To specify the user’s/customers’ requirements, including any constraints and future enhancements,
such that solutions can be identified.
COMPOSITION:
1. General Description/summary;
2. Expected Benefits;
3. Statement of User Requirements:
4. Objectives for the End Product
5. Major Elements to be provided
6. Inputs, Outputs, Formats, Media
7. External Influences and interfaces
8. Security aspects (if any)
9. Strategies:

Implementation, Phasing-in (Pilot/Phased/Incremental/Big Bang)

Education & Training

Documentation

Testing (Individual/Technical/Customer)

Fall-back

Back-up

Data Protection
10. Detailed Requirements:

Detailed Description of Each Major Element (What it is required to do; performance
required)

Constraints:

Development Costs
11.
User/Customer Availability
12.
Operating Considerations
13.
Business Schedule, Target Dates
14.
Probable Future Enhancements:

Short/Medium/Long Term
15.
Glossary of Customer Terms;
FORMAT:
A4 Report format (Supporting Diagrams as appropriate)
DERIVATION:
Sponsors/Users/Customers of the Outcome/End Product.
QUALITY CRITERIA
:
1. Is the Specification a complete and accurate statement of requirements, constraints, and probable
future enhancements?
2. Is it complete as per “COMPOSITION” above?
3. Has the sponsor (at an appropriate level) formally signed-off the Specification?
QUALITY METHOD:
Formal sign-off by both the sponsor and development representatives.
EXTERNAL INFLUENCES
:
Appropriate Users to provide full information about their requirements.
2
SPOCE Project Management Limited - HO0103 v.1
 SPOCETTE - Managing Minor Projects - Project Kick-off Template
APPENDIX C2
SPECIALIST PRODUCT DESCRIPTION
REFERENCE D.2.0 - OVERVIEW OF REQUIREMENTS
PURPOSE:
To identify a set of information system options, each of which would satisfy the requirements to a greater or lesser
extent. To assemble/package all the options considered, during the feasibility study.
Each option presents a
high-level
system design, and is evaluated from the following viewpoints:

business support (the extent of support for business requirements and objectives);

organisational impact on people and concurrent activities;

technical aspects (Information system requirements, viability of development, and implementation
route(s);

financial impact (approximate development, implementation, operational costs).
COMPOSITION;
The overviews of requirements are essentially textual documents, augmented by diagrams where appropriate.
For each option identified:
1.
Heading:

Option name and/or identifier;
2.
Detail comprising:

Textual description (supported by diagrams where appropriate) of the scope of the proposed system
option (clerical/manual and IT aspects), and the requirement to be addressed. This description may
be supported by models of the major processes, inputs, outputs and external interfaces (other
systems and organisations) of the proposed information system.

An overview of the (software and hardware) configuration required to run the information system
option and the technical resources required to develop and/or implement it.

·mpact Analysis - an outline assessment of the impact of the option on the organisation, including
non-financial and indirect benefits.

An outline estimate of the costs of development/implementation.

Estimated resource requirements and outline costs for operation and on-going maintenance.

Outline timescale plan for the development/implementation of the option.

Risk assessment - business, technical, financial and cultural.

Perceived advantages and disadvantages of selecting the option, and a conclusion as to whether it
is achievable and desirable.
FORMAT:
Section of Feasibility Study Report - style consistent with rest of the Feasibility Study Report. Free-format
narrative supported by diagrams, models etc as appropriate.
DERIVATION:

Product - Problem Definition;

User Population; User Management;

Strategy Plan/documentation;

Management Services and IS/IT personnel.
QUALITY CRITERIA:
For each of the options identified:
1. Is the scope of the system described consistent with the constraints defined in the Terms of Reference for the
Feasibility Study Business Case?
2. Is the option feasible from all the following viewpoints:

Strategy;

Business;

Organisational/Cultural;

Technical.
For the set of options:
3
SPOCE Project Management Limited - HO0103 v.1
 SPOCETTE - Managing Minor Projects - Project Kick-off Template

Has the "Do-nothing" option been evaluated?

Is the set of options complete?
QUALITY METHOD:
Formal Quality Review
EXTERNAL INFLUENCES:
User personnel; External advisor(s)/consultant(s).
4
SPOCE Project Management Limited - HO0103 v.1
 SPOCETTE - Managing Minor Projects - Project Kick-off Template
APPENDIX C3
SPECIALIST PRODUCT DESCRIPTION
REFERENCE D.3.0 - DESIGN SPECIFICATION
PURPOSE/DESCRIPTION:
To outline and define the Requirement from a technical viewpoint, and provide a technical design to
plan the development.
COMPOSITION:
1. Summary of Elements/Functions etc Required;
2. Existing Elements Identified:
3. Changes and Impact
4. New Elements Required to be Developed;
5. Specialist Design and/or Plan
6. List of Equipment Required
7. Specialist Specifications for all Equipment to be purchased or developed.
FORMAT:
A4 Report Format or as appropriate.
DERIVATION:

Specialist Product for Specification;

Existing Equipment etc;
QUALITY CRITERIA:
1. Is it complete as per “COMPOSITION” above.
2. Is the Design consistent with the Requirements?
3. Do the Designs/Plans/Specifications adequately describe the equipment etc to a satisfactory
specialist/technical standard?
QUALITY METHOD:
Informal Review and Sign-off by the Project Manager.
EXTERNAL INFLUENCES:
None
5
SPOCE Project Management Limited - HO0103 v.1
  [ Pobierz całość w formacie PDF ]