Академический Документы
Профессиональный Документы
Культура Документы
DOCUMENT IDENTIFICATION
Author Document Location (repository/path/name)
<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Final <Date> Internal
REVISION HISTORY
Version Date Description
0.1 February 4, 2010 <Text here>
0.2
Copyright/Trademark
Table of Contents
Introduction ...................................................................................................................................................... 3
Purpose of this Document ................................................................................................................................. 3
Business Situation / Project background ........................................................................................................... 3
Project Description .......................................................................................................................................... 3
Project Scope .................................................................................................................................................... 3
Project Objectives .............................................................................................................................................. 3
Project Milestones ............................................................................................................................................. 4
Critical Success Factors .................................................................................................................................... 4
Project Organization ........................................................................................................................................ 5
Organization Chart ............................................................................................................................................. 5
Assignments, Roles and Responsibilities for Project <<Project>> ................................................................... 5
Implimentation Strategies ............................................................................................................................... 6
ASAP Implementation Methodology .................................................................................................................. 6
Use of SAP Solution Manager ........................................................................................................................... 7
Organizational Change Management strategy .................................................................................................. 7
Training strategy ................................................................................................................................................ 7
Project Management Plans ............................................................................................................................. 7
Integrated Change Control Procedure ............................................................................................................... 7
Issue Management Plan .................................................................................................................................... 7
Scope Management Plan .................................................................................................................................. 8
Time Management Plan..................................................................................................................................... 8
Cost Management Plan ..................................................................................................................................... 8
Quality Management Plan ................................................................................................................................. 8
HR Management Plan ....................................................................................................................................... 8
Communication Management Plan ................................................................................................................... 8
Risk Management Plan...................................................................................................................................... 9
Procurement Management / Contract Inventory ............................................................................................... 9
Project Standards ............................................................................................................................................ 9
Use of Solution manager ................................................................................................................................... 9
Business Process Modelling Standards .......................................................................................................... 10
Test Management standards ........................................................................................................................... 10
Configuration and development standards ...................................................................................................... 10
Change request and transport management standards .................................................................................. 10
Support package and upgrade standards ....................................................................................................... 10
Technical infrastructure and connectivity ........................................................................................................ 10
Authorization Concept ..................................................................................................................................... 10
Project Logistics and infrastructure ................................................................................................................. 10
Post Implementation services and support Standards .................................................................................... 10
SAP Services deployment plan ....................................................................................................................... 10
Enterprise service standards ........................................................................................................................... 10
Composite application design and development standards ............................................................................ 10
References ..................................................................................................................................................... 11
Copyright/Trademark
Introduction
The Project Management Plan provides information on how the project will be executed, monitored and
controlled, and closed. The project management plan can be either on summary level or detailed, and can
be composed of one or more subsidiary plans and other components, each detailed to the extent required by
the project.
The project management plan provides rules and guidelines that have to be observed by all participants in
the project to ensure the success of the project and should therefore be available to all project participants
for reference.
The Project Management Plan is a working document and will be maintained as necessary by the project
managers (<<Customer>> and SAP Consulting). Changes will be communicated actively to the project
participants.
In addition to the present document a Quality Management Plan formalizes the respective quality aspects for
the project. Contents for both plans should be agreed upon and coordinated between the Quality Assurance
and Project Managers of the project. Both plans need to be considered in parallel and serve as tools to
ensure the success of the project.
<<Describe the business situation that led to the current as-is situation. Provide high-level business
rationale that justifies the initiation of the project >>
Project Description
Project Scope
The scope of the work to be performed during the Project <<Project>> has been endorsed by <<Customer>>
management and contractually agreed with SAP Consulting.
The detail scope can be referenced in the Statement of Work to Professional Services Agreement between
SAP and <<Customer>> (//).
<<Refer to Scope Document xxxxx.doc (//) and/or provide a high-level summary of the scope of the
project.>>
Project Objectives
The objectives of the project are to manage the project and delivery the project scope on time, on budget
and on quality as these relate to fulfilling the expectations of the customer. For further definition and
understanding of the overall project objectives, please refer to the project charter and project scope
documents. These documents should define the expected overall expectations of the project.
The project objectives for <<Project>> are (see also Scope Statement):
Copyright/Trademark
Project Milestones
Following is an overview of the most important milestones for the project:
Milestones/Subprojects Deadline
Project Start 03/03/2009
Preparation <<Project>> 03/28/2009
Blueprint Phase
Realization
<<These milestones should be aligned with the project business case, proposal and /or Statement of Work.
It is important to quantify and qualify the content of each deliverable, ensuring acceptance on both the
content and the timing of each deliverable. It is also important to manage change on these deliverables and
work with the team as changes in the project scope and schedule occur that impact the timing of the
deliverables.>>
<<The project manager is responsible for the success of the project. To ensure this success the project
manager employees different but proven methods of management including all areas of planning and
management control. Project managers must focus on three dimensions of project success. Simply put,
project success means completing all project deliverables on time, within budget, and to a level of quality
that is acceptable to sponsors and stakeholders.>>
Copyright/Trademark
Project Organization
Organization Chart
Project organization provides an overview of the defined project structure, assignment of personnel, and a
high-level definition of roles and responsibilities for all the team members within the project structure.
<<Refer to the project organization, roles and responsibility template in the ASAP roadmap, WBS 1.1.1.2>>
insert Organizational Chart
It is critically important that the roles and responsibilities are well defined for the project activities. Well
defined roles and responsibilities will proive the foundation for team members success, as all team members
will then understand their alignment within the project organization.
<<To facilitate such assignment and to better understand the expected roles and responsibilities of the SC
team, project team members, etc, please refer to Project Organization, Roles & responsibilities document in
ASAP roadmap WBS 1.1.1.2. This templates provides the basis for developing the project organization and
outlines the responsibilities by role for each role possible on the project.>>
Role in SC Name
SC chair <Name Surname>
PRD representation <Name Surname>
PRD representation <Name Surname>
OPS representation <Name Surname>
H/FIN <Name Surname>
H/COS <Name Surname>
H/PER <Name Surname>
<<Customer>> PM <Name Surname>
IT representation <Name Surname>
Copyright/Trademark
SAP IBU representation <Name Surname> (ad hoc to ensure quality for intl. Public
Sector)
SAP Consulting <Name Surname>
SAP Consulting <Name Surname>
Reference project org chart. It is important to define the project team, document the project team and ensure
that all members of the team are aware. This can be done in any format, using the project org chart
structure or any other structure that suites the project team.
Copyright/Trademark
of deliverables that can serve as input to subsequent phases. The ASAP methodology provides sample
deliverables containing a list of outputs and the methods used to produce the deliverable.
Training strategy
<<Outline the chosen training approach for the project>>
Copyright/Trademark
<<Outline connection to Execution, Monitoring and Control procedures (E/M/C) such as : Issue handling and
Issue Log update >>
HR Management Plan
Specifically, Human Resource Management is concerned with the aspect of managing resources on the
project, as they roll on and off the project. In the best case scenario the earlier you engage resources / team
members in the project activities, the higher the likelihood of success. The main focus of the Resource
Management Plan is to develop the basis for managing the processes of this area and producing a
productive, highly efficient and effective team.
<<Outline connection to Execution, Monitoring and Control procedures (E/M/C) such as : Performance
evaluations and appraisal of project team members and partners/sub-contractors>>
Copyright/Trademark
As with the other management areas, it is essential that a communications management plan is developed,
communicated and employed during project execution. It is only through the use of these communication
tools and techniques that the project stakeholders, both internal and external to the project become aware of
the project objectives, issues, milestones and deliverables.
<<Outline connection to Execution, Monitoring and Control procedures (E/M/C) such as : Performance,
status and progress resporting. Development of the comunication matrix used for stakeholder management,
, Escalation procedures >>
Project Standards
Copyright/Trademark
Business Process Modelling Standards
<<For additional information and details about these sections, pls refer to ASAP roadmap>>
System Landscape
<<For additional information and details about these sections, pls refer to ASAP roadmap>>
Authorization Concept
The access for project team to the individual systems and system transactions with the respective
authorization profiles/roles needs to be defined for relevant phase of the project.
Facilities
<<Specify the location(s) and project premises. Clarify the possibility of access to the premises.>>
Copyright/Trademark
REFERENCES
All sources, to which the text refers, are to be specified here, i.e. only one cross reference is inserted in the
appropriate place in the text. That means that no document name or something similar should appear in the
text. In order to keep the document visible and additionally simplify updating, the bibliography always has to
be at the end.
Reference Description
Copyright/Trademark