Project Tracking

Table of Contents Purpose 2 Process Ownership 2 Scope 2 Definitions 2 Roles and Responsibilities 2 Project Management Process Overview 3 Planning Sub-Process 3 Tracking and Oversight Sub-Process 3 Change Management Sub-Process 3 Closeout Sub-Process 3 Metrics 3 Process Escalation 3 Revision History 3 Purpose This document provides a formal approach to managing projects within Company.. Planning Components Inputs Approved Project Charter (include approvals from Product Manager, IT Governance Committee, and Standards Adoption Panel as necessary) Committed Project Sponsor Outputs Approved Project Plan including Project Schedule Tools Templates and examples of relevant artifacts are available in the Group Templates folder under the Project and Process Management folder in FileNet.. Tracking and Oversight Components Inputs Approved Project Plan Outputs Project Reports Updated Project Artifacts (may include Project Plan, Issue Log, Change Management Log, Meeting Notes, Project Reports) Deliverable and Milestone Signoffs Change Requests Tools Templates and examples of relevant artifacts are available in the Group Templates library under Project and Process Management folder in FileNet.. Closeout Components Inputs Project artifacts, including lessons learned documented along the way Outputs Delivered product or service Final project documentation package including a Closeout Report Tools Templates and examples of relevant artifacts are available in the Group Templates library under the Project and Process Management folder in FileNet.. Process Escalation If expectations of this process are not being met, suggestions and concerns should be escalated to: Contact Person Work Phone Cell Phone Revision History Date Author Description 03/31/2000 Initial drafts of separate processes 12/31/2002 Revision to integrate separate sub-processes in a Project Manager Process published 12/31/02 10/08/2004 Change process overviews into swim lane format Miscellaneous content updates and styl