1. P ROJECT C HARTER T EMPLATE V1.0

2. I NTRODUCTION The Project Charter establishes a partnership between the performing and requesting organizations of a project. An approved Project Charter formally initiates a project and is typically used for project kick-off. The Project Manager should ideally participant in creating the Project Charter. The Project Charter provides the Project Manager with the required authority to plan and execute the project. ©Gerhard Consulting. All Rights Reserved.

3. T ABLE OF C ONTENTS Project Purpose & Description Project Objectives High Level Requirements Summary Milestone Schedule Estimated Project Costs / Budget Stakeholder Project Manager Project Organization High Level Risks Training Needs Change Management Technical Decisions Conflict Resolution ©Gerhard Consulting. All Rights Reserved.

4. P ROJECT P URPOSE & D ESCRIPTION o Describe the main purpose or justification of the project. Consider using parts of the business case and other available agreements related to the project. ©Gerhard Consulting. All Rights Reserved.

5. P ROJECT O BJECTIVES o Describe the main objectives of the project. Please consider o Scope o Time o Cost o and other areas of interest ObjectivesSuccess Criteria Sponsor Scope Time Cost xxx ©Gerhard Consulting. All Rights Reserved.

6. H IGH L EVEL R EQUIREMENTS o Define the high level requirements for the product or services for which the project has been set up o Think about using a requirements traceability matrix from the very beginning of the project to properly document each requirement ©Gerhard Consulting. All Rights Reserved.

7. S UMMARY M ILESTONE S CHEDULE o Provide a summary of expected milestones for the product or service of this project. o In case of known time constraints, please describe them here as well. ©Gerhard Consulting. All Rights Reserved. JanFebMarAprMayJunJulAugSepOct Kick Off Start Design Start Build Start Test Go-Live

8. E STIMATED P ROJECT C OSTS / B UDGET o Provide high level estimated project costs and budget for the project. o Depending on information available, describe overall budget and budget for individual project phases. o Use business case information ©Gerhard Consulting. All Rights Reserved.

9. S TAKEHOLDER o List the key stakeholders and describe their role. StakeholderRole ©Gerhard Consulting. All Rights Reserved.

10. P ROJECT M ANAGER o This is to officially nominate and authorize the project manager of the project. o Authorization level should be mentioned here as well ©Gerhard Consulting. All Rights Reserved.

11. P ROJECT O RGANIZATION o Draft a high level org chart for the key areas of the project. Project Managers <> Bus. Owners <> PMO <> Bus. Owners <> Project Managers <> Program Manager <> Development Lead <> Test Lead <> Training Lead <> Functional Lead <> Developer <> Developer <> Developer <> Training SME <> Technical Lead <> Architecture SME <> Test Team <> Functional Team <> Infrastructure SME <> ©Gerhard Consulting. All Rights Reserved.

12. H IGH L EVEL R ISKS o Describe the major known risks and how to mitigate them. #DescriptionImpactProbabilityResponseResponsibleStatus 1Scope changes High75%MitigateJohn Doeopen 2 3 4 ©Gerhard Consulting. All Rights Reserved.

13. T RAINING N EEDS o Describe the known training needs in case of introducing o New software o New products o New services o Organizational changes o Consider also possible training need to deliver the project. ©Gerhard Consulting. All Rights Reserved.

14. C HANGE M ANAGEMENT o Describe the organizational change management need to obtain acceptance for the new product or service coming with the project. ©Gerhard Consulting. All Rights Reserved.

15. T ECHNICAL D ECISIONS o Describe any technical decisions critical for the project. o Architectural changes o Infrastructure changes o Etc. ©Gerhard Consulting. All Rights Reserved.

16. C ONFLICT R ESOLUTION o Describe the process to solve conflicts. Define an escalation path. ©Gerhard Consulting. All Rights Reserved.