BA鼎学友会资料分享--项目章程模板-重要.docVIP

智鼎学友会资料Exchange Infrastructure Project Project Charter Project Charter项目章程Version 1Authors:CUSTOMERNAME NAME Project LeadNAME * Project Lead1 Executive SummaryProject CharterThis Project Charter is intended to set the stage for the successful installation and implementation of the * Exchange Infrastructure Version XXX (* XI XXX) at CUSTOMERNAME. To this end it addresses and details such considerations as Project ScopeProject Management ProceduresImplementation MethodologyProject OrganizationProject Plan and Timelinesamongst others.BackgroundIn order to assess the use of a centralized messaging platform for the integration of diverse systems within the CUSTOMERNAME IT system landscape, * XI was the subject of an initial trial phase (Proof of Concept). The initial trial phase served to evaluate * XI, in particular with respect to the following areasPerformanceMonitoringStabilityFlexibility in interface design (Business Process Management)The results of these trials have shown that significant benefits are to be gained by implementing * XI as the strategic messaging platform. These benefits include improvements in the efficacy of the business processes involved, as well as in the efficiency in operating and maintaining the diverse and distributed IT systems. Following the successful completion of these trials, CUSTOMERNAME has now made the major strategic decision to implement * XI as its central messaging platform. Within the first stage of this implementation, which will be conducted in several distinct steps, CUSTOMERNAME intends to set approximately XX interfaces live by DATE.Table of Contents1Executive Summary22Foreword53Background54General Conditions and Definition of the Project Charter54.1Mission Statement54.2Project Scope, Goals and Objectives64.3Release Strategy64.4Project Duration64.5Project Site64.6Realization Concept74.7Hardware and System Availability74.8Critical Project Success Factors75Project Methodology85.1A* Phases85.1.1Project Preparation85.1.2Business Blueprint95.1.3Realization95.1.4Final Preparation105.1.5Go Live & Support106Description of Activities / Customer Obligation to Cooperate - Regulations Governing Decision-Making and Acceptance106.1Activities to be Performed by *106.2Activities to be Performed by CUSTOMERNAME116.3Specific Activities That Are Not Part of the * Duties127Project Organization, Project and Milestone Plan127.1Project Organization127.1.1Project Manager127.1.2Executive Sponsor137.1.3Steering Committee137.1.4Process Team147.1.5Technical Team147.2Project Plan157.3Tasks / Roles and Responsibilities158Project Procedures168.1Project Management168.2Change-Request Management168.3Task - Issue Management168.4Project Communication Plan168.5Project Documentation178.6Project Environment179Training172 Foreword 前言This Project Charter has been created based on discussions between CUSTOMERNAME (hereinafter referred to as “CUSTOMERNAME” or the “Customer”) and *, and on DOCUMENT from DATE (see App. 1) which was approved by the Steering Committee for the * XI implementation Project (hereinafter referred to as the “Project”). The Project Charter is intended to form the actual basis as to how the Project will be conducted and outlines the project methodology, the aims and the complete scope of the Project. 3 Background 项目背景CUSTOMERNAME has evaluated the use of a centralized messaging platform with a view to improving both the efficacy of its business processes and the overall efficiency in running and maintaining its IT landscape. According to the results of this evaluation, there are a number of significant benefits that can be achieved through the use of * XI as the central hub for data and message exchange between the numerous diverse and distributed systems concerned.CUSTOMERNAME has now made the major strategic decision to implement the * XI software as its centralized messaging platform and this Project has the purpose of realizing this decision.4 General Conditions and Definition of the Project CharterTo define the basic and central elements of the Project, the Project Charter as a single document or collection of documents should be defined by the Project Team. It should be reviewed and approved before commencement of the project. The Project Charter covers the initial planning and preparation of the Project and defines the following aspects: Mission Statement Project scope, goals and objectives Critical Project Success Factors Overall project schedule and sequence of major activities on a high level Establishing the project organization and committees Definition of other project proceduresThe project will be conducted based on the A* (Accelerated *) implementation methodology. This is a highly versatile methodology and will be adapted to the specific needs of the project as appropriate. The A* methodology normally consists of 5 different phases, each of which ends with a short review of the phase and a quality check. These phases are described in more detail in Section 5 Project Methodology.4.1 Mission Statement 任务描述To install, operate and maintain the * XI software as a centralized messaging platform within the existing CUSTOMERNAME IT landscape. 4.2 Project Scope, Goals and Objectives 项目范围，目的和目标The scope of the Project will initially consist of establishing, operating and maintaining a 3-system * XI landscape consisting of the following systems Development (DEV) Quality assurance and test (QA) Productive (PRD)This landscape will be used to develop, test, implement, maintain and operate interfaces between the numerous diverse and distributed CUSTOMERNAME IT systems relevant to key business processes. The exact number and nature of these interfaces will be determined and specified in detail during the Business Blueprint phase.4.3 Release Strategy 策略发布The project will be conducted on the technological basis of the latest * XI release (currently XI Version XX, SP YY) for the particular platform matrix concerned (i.e. taking into account other factors involved such as the database, operating system, etc.).4.4 Project Duration 项目时限According to the current planning, the realization, testing and going-live of the approximately XX interfaces within the framework of the Project should run from DATE1 to DATE2. This corresponds to a project duration of approximately XX working weeks or YY working days. This intention must be reviewed following the completion of the Business Blueprint phase once the exact number, nature and complexity of the interfaces and business processes involved have been determined and specified. Both the project plan and the resources may need to be adjusted following this review.4.5 Project Site 项目地址The sites for carrying out the * consulting activities within the framework of the realization of the Project in accordance with this Project Charter are At the CUSTOMERNAME offices in CUSTOMERSITE At the * offices in Walldorf, after a suitable remote connection has been established.There are a number of advantages to be gained from the setting up of a remote connection, in particular the following: Rapid contact to * Support / Development with improved response time for issue-solving if necessary. Reduced time lost due to traveling which could otherwise be spent working on the project. Cost savings due to reduced travel/hotel costs.Both parties are agreed that, particularly in view of the timelines involved, the setting up of a suitable remote connection for the * colleagues from Walldorf is essential for the successful realization of the project.4.6 Realization Concept 项目实现概念The realization concept should follow the general procedures outlined in this Project Charter and in particular the A* methodology which is detailed in Section 5 Project Methodology. However, due to the tight schedules and deadlines involved in the project, it may be necessary or advisable to conduct certain A* phases in parallel with a degree of overlap. 4.7 Hardware and System AvailabilityThe CUSTOMERNAME * XI installation will operate on a three-system landscape: DEV (development), QA (quality assurance and test), and PRD (productive). The development of interfaces (mappings, routings, BPM) and the unit tests will be carried out on the DEV system. Integration tests will be carried out on the QA system. Access to the DEV and QA systems should be possible for the project team members during the normal office hours (Monday Friday, 06:00-20:00). Access to the system is obviously critical for the realization of the project and any downtimes may lead to delays. CUSTOMERNAME is responsible for the availability of the system and also for any delays or costs that may incur as a result of its unavailability or lack of performance. If the system should not be available for any reason (such as scheduled maintenance etc.), CUSTOMERNAME should inform the * team sufficiently in advance in order to avoid periods of inactivity where the * team would be prepared to work on the system, but would be unable to due to the said downtimes. If such cases should arise, the * team will of course try to change their arrangements as far as possible in order that the time may still be used productively.The conditions above also apply to the remote connection as indicated previously in Section 4.5 Project Site. The remote connection should be made available as early as possible.4.8 Critical Project Success Factors 关键项目成功要素 CUSTOMERNAME and * will jointly provide the leadership and functional skills to assume ownership of the Project and responsibility for the deliverables. Open and frequent communication takes place between Project Management, the Project Team and the Project Steering Committee. The issue resolution process is streamlined. Project scope management must be well planned and monitored. A structured and professional project management methodology is necessary for the successful completion of the Project and it is agreed to use A* as the basis for this.5 Project Methodology 项目方法论The project will be conducted based on the A* (Accelerated *) implementation methodology. This is a highly versatile methodology and will be adapted to the specific needs of the project as appropriate. The A* methodology normally consists of 5 different phases (as shown below), each of which ends with a short review of the phase and a quality check.With Accelerated * (A*), the use of resources for * implementations can be optimized in terms of quality, quantity and time. The results listed in the individual A* phases and activities shall be documented in as much detail as is necessary for achieving these objectives. Focus: Rapid implementation. Ensuring quality and knowledge transfer during implementation. Minimizing costs. Deploying resources efficiently.5.1 A* Phases 项目阶段The A* methodology is divided into the following phases: Project Preparation. Business Blueprint. Realization. Final Preparation. Go Live and Support.5.1.1 Project PreparationThe objective of the project preparation phase is to set the general conditions for successfully implementing the project in cooperation with CUSTOMERNAME. These include: Project charter. Project organization / Structure. Work Breakdown Structure (WBS) with role assignment (see App. 2). Project Plan (see App. 3). Project standards (for example, communication lists, documentation standards, change request procedures). Training programs / training the project members (if necessary). System landscape for the implementation. Installed means of communication (e.g. PCAnywhere/Citrix connection, * Service MP, etc.). *Net connection. Kickoff meeting.5.1.2 Business BlueprintThe concept that is to be realized with the * solution is elaborated in the Blueprint Phase. This phase usually comprises the following: Definition of the organizational structure Defining business processes in Business Blueprint documentsIn a series of interviews the organizational structure and the business processes are discussed. Details of the requirements are elaborated in separate workshops. Each business process is discussed in these workshops. To ensure that customer requirements have been correctly communicated and understood, the Customer signs off the Business Blueprint Documents. The Business Blueprint consists of the organizational structure and a definition of the business processes. In the Project, the Business Blueprint phase basically consists of deciding which interfaces should be realized via XI and then sufficiently detailing the interfaces down to a field level as part of the functional specifications. Certain logical functionality may also be developed within the Business Process Modeller (BPM). These functional specifications must be sufficiently detailed in order to be able to begin working on the realization phase.5.1.3 RealizationThe predefined processes from the business blueprint phase are usually configured during this phase. In the Project, the realization phase comprises carrying out the mappings for the documents and scenarios (interfaces), establishing connectivity between the systems, and where appropriate developing certain business logic within the BPM as defined in the business blueprint phase. The realization phase will also be documented in the form of a technical specification. The realization phase concludes with an integration test, in which the integrated processes are tested and signed off. Configuration and development is usually carried out iteratively in individual, consolidated cycles. End user documentation and end user training documentation if required should be created by CUSTOMERNAME in parallel with the configuration process. This can include support from * consultants if desired by CUSTOMERNAME and agreed with *. As this support is generally not considered in the effort estimations and is thus not part of the agreement it must be agreed separately if desired.5.1.4 Final PreparationThe objective of this phase is to provide a productive system. Components of this phase usually include: End user training (the term “End User” shall mean users accessing the CUSTOMERNAME system) by the key users (the term “Key User” shall mean CUSTOMERNAME employees that have been involved in the Project and have thus acquired adequate knowledge in order to carry out trainings). Stress and volume tests. Planning and implementation. Sign off (approval) of the configured system by CUSTOMERNAME, go-ahead for production startup, and official “go live” of the system.5.1.5 Go Live & SupportIn this phase, end users can receive technical support from key users and * consultants for a period of two weeks (10 working days) after the go live date if this is agreed on between CUSTOMERNAME and *. 6 Description of Activities / Customer Obligation to Cooperate - Regulations Governing Decision-Making and Acceptance 项目活动描述、客户合作的义务Responsibilities and the Customers obligation to cooperate shall be jointly prepared in detail in the scope of the Project Preparation Phase in accordance with the A* methodology for each project team member. The areas of responsibilities and the responsibilities of CUSTOMERNAME and * shall include the provision of the following services, in particular:6.1 Activities to be Performed by *The A* methodology is divided into the following phases:Tasks involved will include:- Checking the prerequisites for the realization package, including the general requirements, estimating additional outlay in terms of time and costs for additional functions / specific services (if necessary).- Monitoring the progress of the tasks assigned to * in accordance with the project plan.- Coordinating the project together with the CUSTOMERNAME project team lead.- Implementing the blueprint (as provided by CUSTOMERNAME), in particular realizing the mappings and configuring the XI system:- Setting up the system landscape directory (SLD) based on the information provided to the * team by CUSTOMERNAME.- Define and develop the interface objects and mapping objects in the XI repository.- Configuration of the integration directory (with regard to sender/receiver relationships).- Configuration of the various adapters involved.- Create technical documentation of the realization work.- Installation of the necessary adapters (under the assumption that the adapters can be installed from CUSTOMERSITE or Walldorf on the CUSTOMERNAME network if this should not be the case, then CUSTOMERNAME may have to install the adapters).If additional effort is required by the * team in order to reach such a stage that interface development work may begin (e.g. preparation work required to fulfill any prerequisites), then * may be entitled to separately invoice this work if it does not form part of the originally estimated effort.6.2 Activities to be Performed by CUSTOMERNAME 客户需要从事的活动Tasks to be performed by the CUSTOMERNAME team members involved in the Project will include:- Providing employees with sound knowledge of the actual processes and who have the decision-making ability and competence to design new processes; these employees shall be released from their other duties to the extent required for the entire duration of the project to carry out Project activities.- Ensuring any prerequisites for the realization package are in place.- Pr