back to notes

How to Develop a Project Charter

How to Develop a Project Charter
Guidelines and Best Practices for developing a Project Charter
• The guidelines and best practices described in this document represent suggested enhancements to maximize the success of project planning activities within our organization

Project Charter Template
• For all projects, start with the Project Charter template in the Enterprise Project Management site.
• Always refer to EPM Deliverable Matrix for minimum content and approval requirements.
• Include EPM ID and Project name as it appears in EPM tool
• For guidance and direction on completing the project charter or assistance with project charter development, consult the Concept BA Team. . Please include the <Project name / EMP Idea or project number> and “Project Charter Assistance” in the Subject line.
Project Purpose
• Describe the project purpose as a business problem or an opportunity statement, why it is being proposed, and who will be impacted by this.
o Include The Problem / Opportunity
o Include who (groups, platforms, customers, etc.) is effected by the Problem/Opportunities (include platforms only for infrastructure/technology projects)
o Include how each group, area, etc. listed is impacted by the Problem/Opportunity (at least a high level statement is included)
• Include any sense of urgency around the project, such as legal or regulatory constraints and/or any dates/timeframes by which the project must complete.
Project Value
• Describe the desired end state and how it will benefit the organization. Include at a high level what a successful solution would provide, create or change, the organization at the business level.
Project Scope
In Scope
• Provide a description of activities that are in scope:
o Are you introducing a new product or service, modifying an existing one or bringing functionality available to other channels online?
o For Secure Session/M2 changes, the assumption is the scope will include (1) all devices (desktop, phone, tablet), (2) all supported desktop and mobile browsers, and (3) all supported operating systems. Any device-specific features must be called out, e.g. gap-fill project for phone only, non-optimized pages for desktop only, etc.
o For mobile applications, if device-specific features are needed, specify whether mobile phone apps (Android, iPhone), Tablet apps (Android, iPad), Text Banking/SMS (Short Message Service), etc. are in scope.
o For phone applications, indicate whether the functionality will be on Native app or M2.
o If you are introducing new functionality or changing existing functionality that offers IL (In Language) capability, indicate whether IL will be impacted.
• Include the user and affected market:
o Specify impacted customer segments/products/channels, if applicable. Specify which customer segment is impacted (e.g. consumer, small business, private bank customers, etc.) and what channels are impacted (e.g. Secure Session, Public Site, CIV, SVP, SVT, IVR, ATM, Contact Centers, etc.).
• Indicate the implementation strategy:
o MVP – Minimum Viable Product
o Slow Roll – Release by market or region with fully developed features
o 100% - Release fully developed features to all markets
• If known, include whether there is vendor work or engagement required for the project.
• Include information regarding key assumptions, design/technical constraints and/or project dependencies/interdependencies, if applicable.
• Specify the requested release for all Epics
• Insert the Epics/Features component here. See Job Aid on how to develop epics/features and the template to use.
• Specify impacted systems engage system architects if there if there are uncertainties about impacted systems.
• If using the workbook, embed the Value Stream Decomposition Workbook.

Out of Scope
• Provide a description of activities markets, products, or systems/platforms that are out of scope.
Benefits Analysis
• Examine the estimated benefits and how their realization is envisioned connecting the organizational strategy to objectives in the project.
• This should include both tangible and intangible benefits to the customer and the business, as presented in the business case.
Expected Project Results
• Specific, beneficial outcomes that define success for the project as presented in the business case.
• The project results must be achievable with the completion of the project deliverables.
Project Schedule
• Estimate the total length of the project, e.g. 18 months, including key milestone dates and expected end date.
• If multiple service or middleware are needed, you may need to plan for them to implement in a prior release to the front-end applications.
• Include the rollout strategy, if applicable, such as a phased regional rollout. What’s the timeframe for the rollout?
• Is a pilot planned? Describe whether the pilot is internal (team members) or for selected external customers, the duration of the pilot and the planned benefits of having it.
Stakeholder Summary
• Include all Business Stakeholders and their responsibilities
• Include all impacted Technology Stakeholders and their responsibilities (include impacted platforms/systems/interfaces, middleware, system of record, third party systems; and how they are impacted, whether test only, new development or changes to existing services)
• If there are any potential compliance and operational risk implications, include all Compliance and Risk Stakeholders that need to be consulted (Note effective Dec 31, 2017, all projects impacting Alerts content or classification, Online Statements, eDocs or Tax documents will require WFVC Legal review, in addition to WFVC Risk Management and LOB Legal and Compliance approvals).
• Include all end-user types and their impacts (include both internal and external customers, e.g. bank customers, customer service representatives)?
• Include Customer and Operational Support areas that are impacted
• If applicable, include all General Ledger/Financial Groups that are impacted
Success Criteria
• Detail key performance indicators (KPI’s) for project success
• KPI’s should be SMART (specific, measureable, attainable, relevant, time bound)
• The success factor includes how it must be measurable and any timeframes for measuring, e.g. reduction in call volumes by 2% per month post implementation
• Include information around volume and number of users if available for measurement
• Does the reporting currently exist or will it need to be built?
• KPI’s should map to items contained in the business case


last updated september 2019