Project Proposal

All project requests should be entered as requests in Planview following the ITS Demand Management Process.

Project Definition & Startup

• M1170: Project Start-up & Kickoff Checklist
  Reminders and checklists for initiating a project and conducting a successful kickoff meeting.

• M101: Project Charge Document
  Name, identify, and define a project scope and requirements. (view sample Project Charge Document )

• M102: Project Plan Schedule Summary
  Project plan information with phases. For use in Excel, MS Project or PlanView. (view sample of PlanView Project Plan)

• M104: Project Issues Log
  Identify issues, changes and risks associated with a project using Lotus Notes or Excel. (view Lotus Notes Database Project Issues Log sample)

• M107: Project Roles, Responsibilities, & Training Requirements
  Outline roles and responsibilities identified for the project. Identify training requirements associated with each role.

• M108: Project Team Communications
  Assign role-specific responsibility for ongoing communications associated with the project. (view sample Project Team Communications document)

• M110: Project Deliverables Log
  Identify and track the required or suggested deliverables for a project based on its specific size or type.

• M111: Project Kickoff Meeting Agenda
  Provide a guide for planning the project kickoff meeting.

Project Execution

• M131: Project Meeting Agenda
  Agenda framework for regular meetings throughout the life of the project.

• M132: Meeting Minutes
  Meeting Minutes template for project meetings.

• M134: Project Variance Report
  PlanView instructions for creating a Project Variance Report.

• M135: Project Status Report
  Lotus Notes instructions for creating weekly Project Status Reports.

• M136: Project Score Card Template
  Use Project Scorecard to indicate project status and milestones

• M137: Lessons Learned (Lotus Notes)
  Example of the Lotus Notes Database to be used for Lessons Learned.

• M104: Project Issues Log
  Identify issues, changes and risks associated with a project using Lotus Notes or Excel.
  (view Lotus Notes Database sample)

Project Health Checks

• M1400A: Project Health Check Approach
  Reference material defining the Project Health Check Approach and its related inputs and deliverables.

• M141: Project Health Check Plan
  Using the associated reference document as needed, define the Project Health Check Plan. (Reference Document)

• M142: Project Health Check Questionnaire & Report
  Complete questionnaire as it pertains to your specific project information.

Post Project

• M190: Project Conclusion Acknowledgement
  Use this form or e-mail to confirm project conclusion.

• M191F: Project Lessons Learned Feedback
  Conduct Lessons Learned meeting and gather feedback from project team members.

• M191S: Project Lessons Learned Summary
  Summarize the Lessons Learned throughout the project. Identify what you think went well, what can be improved, and recommendations for improvement. (View sample)

• M192: Post Project Checklist
  Conclude the project with a thorough review and completion of a final checklist. Wrap up any outstanding action items required for full project closure.

• M193: Project Closure Executive Summary
  Summarize and report project results for ITS Leadership and B&F Executive Officers. This report must not exceed 2 pages.

  Required for all strategic demand type projects, as well as any advanced demand type projects that receive incremental funding, as defined in the ITS demand management process (optional for all other projects but highly recommended in order to capture the business value of ITS effort). This document signifies acknowledgement of project completion. Project Managers should draft the summary and review it with the Project Director and Steering Committee where appropriate. The summary is due within 45 calendar days of your project go-live/completion. When complete, the report is stored in the project documentation repository and also sent via email to Rob Thomas.