Project Charter
Module 01 Project Charter
[Insert Name]
Network Administration Capstone
Module 01 Project Charter
[Insert Name]
Network Administration Capstone
12
Table of Contents
Template Guide 1 1 Executive Summary 2 2 Project Definition 2 2.1 Vision 2 2.2 Objectives 2 2.3 Scope 3 2.4 Deliverables 3 3 Project Organisation 4 3.1 Customers 4 3.2 Stakeholders 4 3.3 Roles 5 3.4 Responsibilities 5 3.5 Structure & Process 7 4 Project Plan 8 4.1 Approach 8 4.2 Overall Plan 8 4.3 Resource Plan 9 4.4 Financial Plan 10 4.5 Quality Plan 10 5 Project Considerations 11 5.1 Risks 11 5.2 Issues 11 5.3 Assumptions 12 5.4 Constraints 12 6 Appendix 12 6.1 Supporting Documentation 12
Template Guide
What is a Project Charter?
A Project Charter is a document which outlines the purpose of the project, the way the project will be structured and how it will be successfully implemented. It describes the project:
·
Vision, objectives, scope and deliverables (i.e. what we have to achieve)
·
Stakeholders, roles and responsibilities (i.e. who will take part in it)
·
Resource, financial and quality plans (i.e. how it will be undertaken). ©
Furthermore:
·
The Project Charter defines the boundaries for the project. It describes in detail the scope of the project, within which all deliverables must be produced. Activities should be undertaken outside the defined scope of the project only if a valid ‘change request form’ has been approved by the Project Sponsor
·
The next stage following approval of the Project Charter is the formal appointment of the project team. ©
How to use this template
This document provides a guide on the topics usually included in a Project Charter. Sections may be added, removed or redefined at your leisure to meet your particular business circumstance. Example tables, diagrams and charts have been added (where suitable) to provide further guidance on how to complete each relevant section.
Note: The template has comments in blue italics that will provide guidance as to what is typically included in each section. Please delete these comments before submitting your completed template.
1 Executive Summary
Executive Summary: Sum up each of the sections in this document concisely by outlining the project:
-Definition
-Organization and plan
-Risks and issues
-Assumptions and constraints.
2 Project Definition
Project Definition: This section describes what the project sets out to achieve. It outlines the vision for the project, the key objectives to be met, the scope of work to be undertaken and the deliverables to be produced.
2.1 Vision
Vision: Describe the overall vision of the project. The vision statement should be short, concise and achievable. Examples of vision statements include:
-To deliver a robust, scalable financial management system to the business.
-To procure new work premises with adequate capacity and functional surrounds.
-To successfully introduce new customer service processes to the marketplace.
2.2 Objectives
Objectives: List the key objectives of the project. Objectives are statements which describe in more detail what it is that the project is going to achieve. All objectives listed should be Specific, Measurable, Achievable, Realistic and Time-bound (SMART).
Business Objectives
List the business-specific objectives to be achieved. For example:
-To deliver new accounts payable and receivable and payroll processes, thereby reducing financial processing timescales by at least 30%
-To build brand new work premises with 50% more space, 30 more cark parks and 20% fewer operational costs than the existing premises
-To provide a new customer complaints service to enable customers to issue complaints on-line and receive a direct response from the company within 24hrs.
Technology Objectives
List the technology-specific objectives to be achieved. For example:
-To install new accounts payable and receivable and payroll system modules within the existing accounting system, thereby achieving 99.5% system up-time
-To relocate existing technology infrastructure at the new building premises within 2 days elapsed time and with no impact on customer service delivery
-To build a new website which allows customers to enter and track complaints through to resolution.
2.3 Scope
Scope: Define the scope of the project in terms of the business:
-Processes which will change
-Organizational areas which will be affected
-Locations which will be impacted on
-Data which will be altered
-Applications which will be installed and/or altered
-Technologies which will be deployed and/or decommissioned©
Where relevant, identify the related business areas which will not be affected as a result of this project.
2.4 Deliverables
Deliverables: Highlight the key project deliverables in table. Use the provided as a guide.
|
Item |
Components© |
Description |
|
New physical premises |
· New physical building
· Interior fit-out
· Telecommunications
|
· 1200 sq m premises near city centre with outdoor facilities, parking and signage · Open plan environment with 5 offices, 3 meeting rooms and a staff games room · Voice / data telecoms infrastructure and video conference facilities
|
|
New financial system |
· Accounts payable module
· Accounts receivable module
· Payroll module
|
· A new system module which enables staff to quickly enter accounts payable transactions · A new system module which enables staff to quickly enter accounts receivable transactions · A new system module which enables staff to quickly enter payroll information
|
|
New customer complaints process |
· Complaints website
· Complaints resolution process
· Complaints measurement process
|
· New website with customer complaints forms, a complaint tracking page and company contact information · New full-time staff complaints role and process for resolving complaints made · New process for assessing complaint characteristics (such as numbers, business areas and resolution timescales)
|
|
|
|
|
|
|
|
|
3 Project Organization
3.1 Customers
Customers: Describe the customers who will use the deliverables produced from the project. Customers may be individuals or groups within or outside of the company. The success of the project will be primarily based on whether or not the deliverables produced match the requirements of the customers identified in this table.
|
Customer |
Expected Use |
|
|
|
|
|
|
|
|
|
|
|
|
3.2 Stakeholders
Stakeholders: List the key stakeholders for this project. A ‘stakeholder’ is simply a person or entity outside of the project who has a key interest in the project. For instance, a company financial controller will have an interest in the cost implications of the project, a CEO will have an interest in whether the project is conducted in accordance with the vision of the company. Examples of stakeholders include:
-Company Executives
-Legislative bodies
-Regulatory bodies.
Use the provided examples as a guide.
|
Stakeholder© |
Interested in |
|
CEO |
Alignment with company vision and strategy |
|
Financial Controller |
Alignment with company budget |
|
Health and Safety Office |
Alignment with health and safety standards |
|
Government body |
Compliance with legislation |
|
Industry body |
Compliance with codes of practice |
|
|
|
|
|
|
|
|
|
3.3 Roles
Identify the roles required to undertake the project. Examples of typical roles include project:
-Sponsor
-Review Group
-Manager
-Team Member
For each role identified, list the resource likely to fill each role and his/her assignment details by completing the following table.
|
Role |
Organization© |
Resource Name |
Assignment Status |
Assignment Date |
|
Role |
Organization |
Person |
Unassigned / Assigned |
xx/yy/zz |
|
|
|
|
|
|
|
|
|
|
|
|
3.4 Responsibilities
Responsibilities: List the generic responsibilities for each role identified. A full list of the responsibilities, performance criteria and skills required should be documented within a separate Job Description for each project role. Use the provided examples as a guide.
Project Sponsor
The Project Sponsor is the principal ‘owner’ of the project. Key responsibilities include:
· Defining the vision and high-level objectives for the project
· Approving the requirements, timetable, resources and budget
· Authorizing the provision of funds / resources (internal or external)
· Approving the project plan and quality plan
· Ensuring that major business risks are identified and managed
· Approving any major changes in scope
· Receiving Project Review Group minutes and taking action accordingly
· Resolving issues escalated by the Project Manager / Project Review Group
· Ensuring business / operational support arrangements are put in place
· Ensuring the participation of a business resource (if required)
· Providing final acceptance of the solution upon project completion.
Project Review Group
The Project Review Group may include both business and 3rd party representatives and is put in place to ensure that the project is progressing according to plan.
Key responsibilities include:
· Assisting the Project Sponsor with the definition of the project vision and objectives
· Undertaking Quality Reviews prior to the completion of each project milestone
· Ensuring that all business risks are identified and managed accordingly
· Ensuring conformance to the standards and processes identified in the Quality Plan
· Ensuring that all appropriate client/vendor contractual documentation is in place prior to the initiation of the project.
Project Manager
The Project Manager ensures that the daily activities undertaken on the project are in accordance with the approved project plans. The Project Manager is responsible for ensuring that the project produces the required deliverables on time, within budgeted cost and at the level of quality outlined within the Quality Plan.
Key responsibilities include:
· Documenting the detailed Project Plan and Quality Plan
· Ensuring that all required resources are assigned to the project and clearly tasked
· Managing assigned resources according to the defined scope of the project
· Implementing the following project processes: time / cost / quality / change / risk / issue / procurement / communication / acceptance management
· Monitoring and reporting on project performance (re: schedule, cost, quality and risk)
· Ensuring compliance with the processes and standards outlined in the Quality Plan
· Reporting and escalating project risks and issues
· Managing project interdependencies
· Making adjustments to the detailed plan as necessary to provide a complete picture of the progress of the project at any time.
Project Team Member
A Project Team member undertakes all tasks necessary to design, build and implement the final solution.
Key responsibilities include:
Undertaking all tasks allocated by the Project Manager (as per the Project Plan)
Reporting progress of the execution of tasks to the Project Manager on a frequent basis
Maintaining all documentation relating to the execution of allocated tasks
Escalating risks and issues to be resolved by the Project Manager. ©
3.5 Structure and Process
Structure: Depict the reporting lines (a.k.a. organizational chart) for each of the key roles.
Process: In addition, provide a thoughtful and proactive approach to working with a multinational team, including multiple avenues to ensure empathy and respect for difference. Include strategies for maximizing communication and collaboration despite differences in language, customs, and norms.
4 Project Plan
4.1 Approach
Approach: Describe the approach to be taken to implement each of the phases within the project. Use the provided examples as a guide.
|
Phase |
Approach© |
|
Initiation |
Outline the method by which the project will be further defined, the project team appointed, and the Project Office established. |
|
Planning |
Define the overall planning process to ensure that the phases, activities and tasks are undertaken in a co-ordinated fashion. |
|
Execution |
Describe the generic phases and activities required to build, test and implement the deliverables of the project. |
|
Closure |
Describe the steps required to release the deliverables to the business, close the project office, reallocate staff and perform a Post Implementation Review of the project. |
4.2 Overall Plan
Overall Plan: Provide a summarized plan outlining the sequence of each of the phases listed above. A more detailed Project Plan will be drawn up during the “Planning” phase of the project.
Milestones Milestones: A sub-section of the Project Plan. List the major project milestones and the required delivery dates. A ‘milestone’ is a significant event or stage to be completed. Explain why each milestone is critical to the project.
|
Milestone |
Date© |
Description |
|
Milestone Title |
xx/yy/zz |
Explain why milestone date is critical to business |
|
|
|
|
|
|
|
|
|
|
|
|
Dependencies
Dependencies: List any project activities which:
-Will impact on another activity external to the project
-Will be impacted on by the non/delivery of another activity external to the project
For example (if our project was to build a house):
1. Painting the walls is dependent on completing the drywall.
2. Completing the drywall is dependent upon completing the framing.
3. Completing the framing is dependent upon completing the foundation.
|
Project Activity |
Impacts on |
Impacted on by |
Criticality© |
Date |
|
Planned Activity |
External Activity |
External Activity |
Low/Medium/High |
xx/yy/zz |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4.3 Resource Plan
Resource Plan: Summarize the duration and effort required for each project team member. A detailed Resource Plan will be drawn up during the “Planning” phase of this project.
|
Role |
Start Date |
End Date |
% Effort |
|
Project Role |
xx/yy/zzzz |
xx/yy/zzzz |
xx/yy/zzzz |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4.4 Financial Plan
Financial Plan: Summarize the project budget approved. Use estimates for this portion and also use the provided examples as a guide for items to include in the budget. A detailed Financial Plan will be drawn up during the “Planning” phase of this project.
|
Category |
Cost© |
Value |
|
People
|
· Salaries of project staff · Contractors and outsourced parties · Training courses |
$ x $ x $ x
|
|
Physical |
· Building premises for project team · Equipment and materials · Tools (computers, cabling, phones…) |
$ x $ x $ x
|
|
Marketing |
· Advertising / branding · Promotional materials · PR and communications |
$ x $ x $ x
|
|
Organizational |
· Operational downtime · Short-term loss in productivity · Cultural change |
$ x $ x Describe
|
|
|
|
|
|
|
|
|
4.5 Quality Plan
Quality Plan: Briefly describe the various processes to be undertaken to ensure the success of the project. A detailed Quality Plan will be drawn up during the “Planning” phase of this project.
|
Process© |
Description |
|
Quality Management |
Summary of how the process will be undertaken |
|
Change Management |
|
|
Risk Management |
|
|
Issue Management |
|
|
Configuration Management |
|
|
Document Management |
|
|
Acceptance Management |
|
|
Procurement Management |
|
|
Financial Management |
|
|
Timesheet Management |
|
|
Project Reporting |
|
|
Project Communications |
|
|
|
|
|
|
|
5 Project Considerations
Project Considerations: These are elements that must be considered during the project lifecycle
5.1 Risks
Risks: Summarize the most apparent risks associated with the project. Risks are defined as “any event which may adversely affect the ability of the solution to produce the required deliverables”. Risks may be Strategic, Environmental, Financial, Operational, Technical, Industrial, Competitive or Customer related. To complete this section thoroughly, it may be necessary to undertake a formal Risk Assessment (by documenting a Risk Management Plan). To reduce the likelihood and impact of each risk's eventuating, clear ‘mitigating actions’ should be defined. Use the provided examples as a guide.
|
Description |
Likelihood |
Impact© |
Mitigating Actions |
|
Inability to recruit skilled resource |
Low
|
Very High |
Outsource project to a company with proven industry experience and appropriately skilled staff |
|
Technology solution is unable to deliver required results |
Medium |
High |
Complete a pilot project to prove the full technology solution |
|
Additional capital expenditure may be required in addition to that approved |
Medium |
Medium |
Maintain strict capital expenditure processes during the project |
|
|
|
|
|
|
|
|
|
|
5.2 Issues
Issues: Summarize the highest priority issues associated with the project. Issues are defined as “any event which currently adversely affects the ability of the solution to produce the required deliverables”. Use the provided examples as a guide.
|
Description© |
Priority |
Resolution Actions |
|
Required capital expenditure funds have not been budgeted |
High |
Request funding approval as part of this proposal |
|
Required computer software is only at ‘beta’ phase and has not yet been released live |
Medium |
Design solution based on current software version and adapt changes to solution once the final version of the software has been released |
|
Council approval must be sought to implement the final solution |
Low |
Initiate the council approval process early so that it does not delay the final roll-out process. |
|
|
|
|
|
|
|
|
5.3 Assumptions
Assumptions: List the major assumptions identified with the project to date. Examples include:
-There will be no legislative, business strategy or policy changes during this project
-Prices of raw materials will not increase during the course of the project
-Additional human resources will be available from the business to support the project.
5.4 Constraints
Constraints: List the major constraints identified with the project to date. Examples include:
-The financial budget allocated is fixed and does not allow for over-spending
-There are limited technical resource available for the project
-The technical solution must be implemented after-hours to minimize the operational impact on the business.
6 Appendix
Appendix: This section may or not be required.
6.1 Supporting Documentation
Attach any documentation you believe is relevant to the Project Charter, including:
-Curricula Vitae (CVs) for key project staff
-Approved Business Case
-Approved Feasibility Study
-Research Materials
-External quotes or tenders
-Detailed financial planning spreadsheets
-Other relevant information or correspondence.