1. Tools: Project Charter (Tab 4)

2. TRAINING EXPECTATIONS
At the end of this module, participants will be able to:
Demonstrate how the Project Charter applies to their work.

3. PROJECT CHARTER Project title: Charter is assigned by:
Brief, general description of project assignment:
Problem description:
All or any expected outcomes (include minimums & priorities):
All parameters (conditions, boundaries, constraints, design criteria) relevant to the effort:
Clearly described decision-making authority boundaries and flexibilities between the Sponsor(s) and the PL/team:
Method by which the Sponsor(s) PL/PM/Team will communicate with and support each other:
Perspectives and expectations on how to go about the work:
Names, role and responsibilities of all team members, management sponsors, etc.
Signature blocks:
Area Manager
Program Manager(s)
Project Leader
Project charters are a tool to provide a means for mutual alignment, support and commitment between the project sponsors (such as the Area Managers, District Manager or even external partners), the Program Managers who are providing the funding (such as Bridge or Interstate Maintenance) and those who are charged with delivering the project.( such as the Project Leader, Project Team members)
They are typically co-drafted and negotiated by the Project Sponsor and the person assigned to deliver the project.
Team understanding and agreement on what is to be solved and how is essential.
Discussions matter.
Reaching consensus matters.
Active involvement by all matters.
Prospectus and consultants contracts are more formal documents we have used to define project requirements. The Charter is less formal, can be adapted to individual project needs – but just as binding
We will undoubtably have overlap in project documentation for awhile as we embark with this new tool. But over time we will become more efficient in this area.

4. Project Charter Project title: ___ Charter is assigned by: ___
Brief, general description of the project assignment: ___
Problem description: ___
All or any expectations and outcomes (include minimums & priorities): ___
All parameters (conditions, boundaries, constraints, design criteria) relevant to the effort: ___

5. Project Charter
Clearly described decision-making authority boundaries and flexibilities between the Sponsor(s) and the PL/PM/Team: ___
Method by which the Sponsor(s) PL/PM/Team will communicate with and support each other: ___
Perspectives and expectations on how to go about the work: ___
Names, roles and responsibilities of all team members, management sponsors, etc.: ___
Signature blocks:
Area Manager
Program Manager(s)
Project Leader

6. MOUs, IGAs, and Charters MOUs, IGAs:
Stand alone legally binding documents between government entities defining roles and fiscal responsibilities
Charters:
Flexible, informal, internal expectations document, clarifying nuances around purpose and need, priorities, etc.
Commitment between project sponsor and project team on what and how to deliver
Elements from these or any other project-related documents can be incorporated across each other, and should be supportive and helpful to provide consistency, direction, etc.

7. Project Charter… Planning for Success!
Excellent tool to clarify, agree on and document Purpose and Need
Opportunity to identify successful delivery of S.C.O.P.E. values
Good idea to include key stakeholders, knowledge experts and decision makers during Charter development
Helps in documenting critical decisions
Commitment from Program / Sponsor / PL-PM / Team
Use Charter to facilitate ongoing project management

8. Success Indicators – Charter
All projects have Charters
Charters are realistic, “doable” and jointly owned.
At the end, the Sponsor and Team agree…“This was a good project!”

10. “insert Region specific slides here!”
Project Charter Process
Mod 3 - slide 9 -
Reg ? – Project Charter

11. Region ? Next Steps ?
Reg ? – Project Charter