Project Management Methodology
This page and all documents linked to this page
are:
Copyright © 2008 The Regents of the University of Michigan
Important: These documents are made available by ITS for
public use, on an "as is" basis, without warranties of
any kind, express or implied, including merchantability or fitness
for a particular purpose.
The Project Management Methodology is designed for use in managing the Information and Technology Services (ITS) projects. Click on a phase below for a detailed workflow.
The scope, size, and complexity of a project will affect the number of deliverables, which should be produced in order to adequately manage the proposal and execution of the project.
Note: Office 2007 is used for some Project Managment documents. If you do not have this software, you can download the Microsoft Office compatibility pack.
back to top
back to top
back to top
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 projects over 500 hours of effort as defined in the ITS Project Proposal process (optional for projects under 500 – but highly recommended in order to capture the business value of ITS efforts). 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. |
back to top
|
