0. [Your Project Name] Kick-Off Meeting Month, Year

1. Agenda Background Project Approach & Timeline
Project Assumptions & Constraints
Roles & Responsibilities
Project Governance
Next Steps
Question & Answer

2. Background
The project was initiated to:
Goals.

3. Project Approach The project will take a phased approach
Outreach & Requirements: [Dates; Notes]
Design Phase: [Dates; Notes]
Implementation Phase: [Dates; Notes]

4. Project Timeline
January
February
March
April
May
June
July
August
Sept
October
November
December
Requirements
Scope Defined
Design
Build
Implementation
Build & Implementation Complete
Testing
Project Management, Weekly Meetings; Communications Embedded in the Project Lifecycle

5. Project Assumptions Functional Infrastructure Requirements #1 2 3

6. Project Constraints
Constraints #1 2 3

7. Project Governance [Name] Project Sponsors Project Management Approach
Assist in strategic planning with campus partners to ensure alignment of desired success criteria and project delivery
Leverage centralized project workspace to collaborate with project team and stakeholders
Provide standardization in planning, scheduling, reporting and control
Establish weekly project management meeting
Store documents in centralized repository

8. High Level Communications Plan
Area
Activity Area(s)
Audience
Ownership
Timeline/
Frequency
Executive
Monthly meeting
Bi-weekly reporting as requested
Project Executive Committee
Project Lead; Computing Services Sponsor
Monthly and more frequently as appropriate
Internal Stakeholder Outreach & communications
Team site
Functional requirements meetings
Ad-hoc communications
Computing Services, and Campus Stakeholders
Project Lead
Examples – ongoing communications activities
Standard Project Reporting & Communications
Monthly status report
Meeting notes & actions
Project schedule & milestone progress reporting
Project team; Stakeholders
Weekly – ongoing communications activities

9. Roles & Responsibilities
Name
Role
Project Activities
Functional Project Lead
Outreach to campus; Project direction
Computing Services sponsor
Computing Services relationship with campus; Resource management; technical guidance
Technical Lead
Technical leader in requirements elicitation and analysis; facilities planning, design, and deployment planning
Project Lead
Project management best practices

10. Risk Management # Risk Element Risk Response 1 Schedule Delays -
Conduct project planning to create detailed schedule.
Use PM resource to manage the schedule 2
CMU Resource Constraints;
Engage sponsor groups
Communicate deadlines
Identify critical path elements for focused work activities. 3 4 5 6

11. Next Steps Upcoming Milestones – Next 30 Days Task
Expected Completion Date

12. Comments & Questions