DOCX

Project Charter Template

By Jeffery Parker,2014-07-09 10:04
9 views 0
Project Charter Template

    Project Charter

    for

    

    Version 1.0 approved

    Prepared by

    

    

    Copyright ? 2007 by Karl E. Wiegers. Permission is granted to use and modify this template.

Project Charter for Page ii

    Table of Contents

    1. Project Description .................................................................................................... 1 2. Business Objectives and Success Criteria .................................................................. 1 3. Stakeholders .............................................................................................................. 1

    4. Vision ........................................................................................................................ 1

    5. Project Scope ............................................................................................................. 2

    6. Assumptions and Dependencies ................................................................................. 2 7. Constraints ................................................................................................................ 2

    8. Milestones ................................................................................................................. 3

    9. Business Risks ........................................................................................................... 3

    10. Resources .................................................................................................................. 3

    11. Approvals .................................................................................................................. 4

    Revision History.............................................................................................................. 5

Project Charter for Page 1

    1. Project Description

    describe the business opportunity that the project is intended to create or exploit. There might be a specific final deliverable or goal to call out. You could incorporate a summary of the business case that explains why the organization wants to undertake the project.> 2. Business Objectives and Success Criteria

    measurable. These could include revenue increase, cost savings, return on investment, or target release dates. Determine how success will be defined and measured on this project. Describe the factors that are likely to have the greatest impact on achieving that success. Establish measurable criteria to judge whether project has met its business objectives.> 3. Stakeholders

    are affected by its outcome, or can influence its outcome. The stakeholder profiles identify the project sponsor, project manager, customers for this product, and other stakeholders. Identify business-level customers, target market segments, and significant user classes. For each stakeholder category, describe the major benefits they will receive from the product, their likely attitudes toward the project, what constitutes a win or success for the stakeholder, and any known constraints that must be accommodated. You might include a table that lists affected business areas and organizations and describes the impact the project will have on them.>

Stakeholder Major Benefits Attitudes Win Conditions Constraints

    Project

    Sponsor

    Project

    Manager

    User Class #1

    User Class #n

    etc.

    4. Vision

    describes what the world will be like when the project is completed. The vision statement should reflect a balanced view that will satisfy the needs of diverse customers as well as those of the developing organization. It may be somewhat idealistic, but it should be grounded in the realities of existing or anticipated customer markets, enterprise architectures, organizational strategic directions, and cost and resource limitations. Consider using the following template:

For (target customer)

    Who (statement of the need or opportunity)

    The (product name)

    Is a (product category)

Project Charter for Page 2

    That (key benefit, compelling reason to buy or use)

    Unlike (primary competitive alternatives, current system, or current business process) Our product (statement of primary differentiation and advantages of new product or service)> 5. Project Scope

    deliver. Scope can be represented using a context diagram, an event list, and/or a feature table. Scope might be subdivided into the scope of the initial product release and planned growth strategies for subsequent releases. It’s also important to define what the project will not include,

    so describe limitations and exclusions, such as product features or characteristics that a stakeholder might anticipate, but which are not planned to be included in the project.> 6. Assumptions and Dependencies

    project. Note any major external dependencies the project must rely upon for success, such as specific technologies, third-party vendors, development partners, or other business relationships. Also identify any other projects that are related to this project in some way or may have a bearing on its outcome. Give each item a unique identifier, like those shown below.>

AS-1:

    DE-1:

    7. Constraints

    interfaces to other projects or products, or technologies to be employed. Describe the priorities among the project’s features, quality objectives, schedule, staff, and budget. The following table identifies the parameters around the project’s key drivers (top priority objectives), constraints to

    work within, and dimensions that can be balanced against each other to achieve the drivers within the known constraints. Example:>

    Constraint Driver Degree of Freedom Dimension (state limits) (state objective) (state allowable range)

    Features 70-80% of high priority

    features must be included in

    release 1.0

    Quality 90-95% of user acceptance

    tests must pass for release

    1.0, 95-98% for release 1.1

    Cost budget overrun up to 15%

    acceptable without executive

    review

    Schedule release 1.0 to be

    available by 10/1, release

    1.1 by 12/1

    Staff maximum team size is

    6 developers + 4

    testers

Project Charter for Page 3

    8. Milestones

    role or individual who is responsible for each one. It's not necessary to include the target date for each milestone unless they are fixed constraints. The following table illustrates some typical milestones; change this list as appropriate for your project.>

    Event or Deliverable Target Date Responsibility

    Project charter approved

    Project plan completed

    Project plan approved

    Project team assembled

    Project execution initiated

    Project execution completed

    Customer acceptance

    Project closed out

    9. Business Risks

    competition, timing issues, user acceptance, implementation issues, or possible negative impacts on the business. Estimate the severity of each risk’s potential impact and identify any

    risk mitigation actions that could be taken. This is not the place for the project’s overall risk list.>

    Risk Probability Impact Mitigation

10. Resources

    time. Human resources include key individuals, teams, organizations, subcontractors or vendors, and support functions. This is not the place for the detailed team staff roster of individual names. Identify critical skill sets that team members must have. Other resources could include funding, computers, other equipment, physical facilities such as buildings and rooms, hardware devices, software tools, and training. If the project team organization is known at the time of chartering, include that information here, perhaps in the form of an organization chart.>

    Resource Description and Source

Project Charter for Page 4

    Approvals

    positions of the individuals who must approve the charter, particularly the project sponsor. You may wish to add some descriptive text to make sure all of these individuals agree on what their signature of approval means. For example, approving the charter could mean that the signatory agrees with the content as presented here, agrees to use this charter as a basis for the project, and agrees to keep the information in the charter current and relevant.>

Approval Decision:

; Approved, development of detailed project plan is authorized

    ; Approved, project execution is authorized

    ; Approved, but project is on hold until future notice

    ; Revise charter and resubmit for approval

    ; Charter and project proposal are rejected

    Role or Title Name and Signature Date

Project Charter for Page 5

Revision History

Name Date Reason For Changes Version

Report this document

For any questions or suggestions please email
cust-service@docsford.com