DIRECTIVE NUMBER: v2.0. SUBJECT: Correctional Integration Systems Change Management Plan

Size: px
Start display at page:

Download "DIRECTIVE NUMBER: 141.03.04.001 v2.0. SUBJECT: Correctional Integration Systems Change Management Plan"

Transcription

1 DEPARTMENT OF CORRECTION SUPPORT Management Services DIRECTIVE NUMBER: SUBJECT: Correctional Integration Systems Change PAGE NUMBER: 1 of 10 Adopted: POLICY OF THE DEPARTMENT It is the policy of the Board of Correction that the Department of Correction shall establish guidelines for the efficient and appropriate use of computers, electronic mail ( ), and the Internet by Department employees PURPOSE The change management process is fundamental to the successful delivery of a computer development project. The change management process ensures that each change identified within the project environment is documented, prioritized and resolved within an appropriate time scale. For the purpose of any project, changes are defined as any event which adversely affects the ability of the project to produce the required deliverables. Change management will be introduced to the Correctional Integration Systems (CIS) project through the implementation of five (5) key formalized processes: identification of project changes; logging and prioritization of project changes; assigning change actions; implementation of change actions; and the closure of project changes TABLE OF CONTENTS POLICY OF THE DEPARTMENT PURPOSE TABLE OF CONTENTS REFERENCES DEFINITIONS SCOPE RESPONSIBILITY PROCEDURE FLOWCHART REFERENCES Attachment A, Change Request Form. Attachment B, Change Register.

2 2 of 10 Department Policy 141, Computer, Electronic Mail, And Internet Use DEFINITIONS Change. To pass or make something pass from one state or stage to another; making or becoming different: alteration, variation, or modification, or the result of this. Change Requestor. The person who submits the change request. Department. The state Department of Correction. End User Steering Committee (EUSC). A collective group of individuals chosen to represent each area of the Department. This committee receives, reviews, assesses, and makes recommendations for new and enhancement projects. Stakeholder. One who has a share or an interest in the outcome of a system or project SCOPE Identify Change This process provides the ability for any stakeholder to raise a project-related change. The following procedures are undertaken: Change requestor identifies a change applicable to a particular aspect of the project (e.g. scope, deliverables, time scales, and organization); Change requestor completes a change form and distributes the form to his manager for approval; and Manager approves change request and distributes to project manager. (See sub-section ) Register Change This process allows the project manager to review all changes raised and determine whether or not each change is applicable to the project. This decision will be primarily based upon whether or not the change: impacts a project performance; impacts the budget deliverable specified; or impacts the time scale specified within the project plan.

3 3 of 10 If the change is considered by the project manager to be appropriate to the project, then a formal change is raised in the project change register and a change number assigned. If a change is considered by the project manager to be inappropriate to the project, then the specific problem may be escalated to executive management. Detailed notification will be sent to all stakeholders soliciting feedback prior to change actions being assigned. The project manager will either assign the change priority based upon the level of impact of the change to the project or escalate the change to the End User Steering Committee. If the change is determined to be minor, already included in scope but previously missed, or is an enhancement request and does not require a large development effort, the project manager has the authority to approve the change without having to consult the End User Steering Committee Assign Change Actions This process involves the formal review of the change register by the End User Steering Committee. The End User Steering Committee will review each change and in turn (based upon change priority) may decide to: close the change in the change register, if there are no outstanding change actions and the change is no longer impacting the project; or raise a project risk if the change is also likely to impact the project in the future; approve and assign change actions Implement Change Actions This process involves the implementation of all actions assigned by the project manager or End User Steering Committee. This includes: Scheduling each action for completion; Implementing each action scheduled; Reviewing the success of each action completed;

4 4 of 10 Communicating the success of each action completed; The regular review of all issues recorded in the change register; The identification of issues which require change requests and/or project risks to be raised; and The determination of what actions must or should be taken to resolve, close, or assign the change for completion Close Change A change request can be considered closed when it has no outstanding actions or no longer impacts the project. The project manager maintains and distributes a change register. Upon project completion all change information is included and archived with project documentation RESPONSIBILITY Change Requestor The change requestor initially identifies the change and formally communicates the change to the functional manager. The change requestor is formally responsible for: The early identification of the change within the project; form; The formal documentation of the change, through the completion of the change The submission of the change form to their immediate functional manager for review; and Ensuring change form is complete and contains all applicable data for approval by the appropriate functional manager Development Staff The development staff are responsible for the following: Gaining a thorough understanding of the identified change request as it is applied to the Department's internal business requirements;

5 5 of 10 Identifying the scope, benefits, or possible drawbacks of the requested change; Support and research of the outlined changes; Making the actual enhancements to the system; Reporting the system change results to the project manager; Notifying the project manager if the scope of the change is altered by unforeseen challenges; Support and adhere to established Department policies and procedures; and Support the implementation, training, and transition of the change End User Steering Committee The End User Steering Committee determines the change status and assigns change resolution actions where appropriate. The End User Steering Committee is formally responsible for: The regular monthly review of all changes escalated in the change register; The identification of changes which require change requests and/or project risks to be raised; The determination of change resolution actions while adhering to proper quality control standards; and Provides approval on change management costs, schedules, and deliverables Managers (Subject Matter Experts) Each individual area manager is responsible for the following if the change request that has occurred affects their modules in any way: Reviews and approves user change requests prior to submission; Liaison between the project team and the end user community; Responsible for the coordination of end user participation in the change management process (such as testing newly changed item);

6 6 of 10 Ensure all user testing is completed in a timely and accurate manner; Work with end users to validate and improve system performance; Support and adhere to established Department policies and procedures; and Knowledge base resource for clarification of complex user functional questions as they apply to change requests Project Manager The project manager receives, records, monitors and controls the progress of all changes within a project. The project manager is formally responsible for: Reporting and communicating all decisions made to the End User Steering Committee; Provides detailed change notification to all stakeholders requesting feedback (this must contain the applicable data necessary for each module to determine if the change will have a negative effect); Responsible for ensuring all project team members and stakeholders are aware of change proposals and allow for feedback; Receiving all change forms and identifying which of the changes raised are appropriate to the project; Recording all changes deemed appropriate to the project, in the change register; Prioritizes all changes in the change register as initiated by the End User Steering Committee; The closure of changes which have no outstanding actions and are no longer impacting the project; Monitoring the progress of all change resolution actions assigned; Ensures all change actions are completed in a timely manner; Completion and update of the knowledge registry upon project completion (this document will remain with the project documentation).

7 Project Team 7 of 10 The project team undertakes all change resolution actions delegated by the project manager Quality Assurance Lead (if applicable) The quality assurance lead is responsible for overseeing the validation of the system and ensuring that quality assurance standards are adhered to during the change management process: Manages the adherence to defined software development and quality assurance standards and reporting status to project manager; Obtains a thorough understanding of the business problem that initiated the change request, user objectives and expectations; and Works closely with development staff to prepare user documentation changes (if applicable) prior to change being made in production environment PROCEDURE The change request form should be completed by the change requestor, validated and signed off by his manager (if applicable) and formally distributed to the project manager for review. The project manager will determine whether or not the form provides adequate information and whether the change requires escalation to the End User Steering Committee for approval. The project manager may request that more information be provided. Following the completion of information gathering, the change documentation will be presented to the End User Steering Committee for review and detailed information will be forwarded to all stakeholders for review and feedback. If the End User Steering Committee determines the change to be beyond their scope, will extend the project timeline greater than a month, or requires additional funding of greater than fifteen thousand dollars ($15,000), the change will be referred to the executive management team for a decision.

8 8 of 10 The project manager will monitor the status of the change request and communicate the final decision to the End User Steering Committee, change requestor, and all stakeholders FLOW CHART The following diagram provides an overview of the change processes and procedures to be undertaken in order to effectively manage project-related changes. Change management roles have also been allocated. (See Flow Chart located on page nine.)

9 9 of 10 Change identification Change identified by requestor Approved by Manager Yes No Change Form submitted to PM Change review ed by PM Within PM authority to assign? Register change Detailed notification sent to stakeholders Feedback Received? No Change review ed by EUSC Yes Assign change actions Change actions assigned Implement change actions Does chg require escalation? Does chg raise new risk? Yes Refer to risk mgmt plan Yes No No Executive team Review Yes Change actions completed Is chg approved? no Close chg request and update register Update know ledge registry

10 SUBJECT: Change Management 10 of 10 Administrator, Support Date

11 Idaho Department Of Correction Change Request Form In order to initiate a change request, please complete the following form. All applicable sections MUST be completed. Attach to this form any supporting documentation, which may assist the review of this change request. Please sign and date the Change Request Form and forward it along with any supporting documentation to the Project Manager for review. (See Change Request Form on next page.) , Attachment A, Page

12 Change Number (unique number based upon project): e.g. project number followed by Department and issue number 295 TES1 Change Request Form Business Area/Location: Change Requestor: Project Name: Change Request Date: Project Manager: Change Urgency: Critical High medium low Change Description: Add a brief description of the project changes requested. This should include any changes to resources, deliverables, timescales and/or budgets Business Drivers: List any business drivers which necessitate this change (e.g. recent change in safety policy) Business Impact: Describe the impact to the business if this change is implemented (e.g. additional resources required, reduce process efficiency, organizational structure changes required) Change Benefits: Describe the financial and non-financial benefits associated with the implementation of this change (e.g. reduced transaction costs, improved performance, enhanced customer satisfaction) System Drivers: (IS will evaluate if required) List any system drivers which necessitate this change (e.g. reduction in system performance, lack of vendor support) Systems Impact: (IS will evaluate if required) Describe the impact to IT systems if this change is implemented (e.g. integration required, temporary down-time, new systems processes required) if applicable user will have to contact technical services for this information. Change Costs: Describe the financial and non-financial costs associated with the implementation of this change (i.e. budget required, temporary reduction in staff performance) Supporting Documentation: Add any documentation references which may substantiate this change Signature: Date: / / PLEASE FORWARD TO YOUR FUNCTIONAL MANAGER FOR APPROVAL PRIOR TO SUBMISSION TO THE PROJECT MANAGER , Attachment A, Page

13 Idaho Department Of Correction Change Register The Change Register is the log within which all issues are registered and tracked through to resolution. Status A=Active H= Hold C=Complete Change Register KEY L = Low M = Medium H = High C = Critical Project Name: Project Manager: Date Raised Raised By Assessed By Status Description of Change Description Approval Implementation Description of Impact Impact Rating (L/M/H/C) Change Approver(s) Approval Status Approval Date Actions Undertaken Completion Date Review Date , Attachment B

LGS Project Management Methodology

LGS Project Management Methodology Page: 32 LGS Project Management Methodoy The LGS project management methodoy is integral to our overall delivery methodoy. Based on inpro, one of the LGS inspiration series documents, our methodoy is compliant

More information

Minnesota Health Insurance Exchange (MNHIX)

Minnesota Health Insurance Exchange (MNHIX) Minnesota Health Insurance Exchange (MNHIX) 1.2 Plan September 21st, 2012 Version: FINAL v.1.0 11/9/2012 2:58 PM Page 1 of 87 T A B L E O F C O N T E N T S 1 Introduction to the Plan... 12 2 Integration

More information

Project Role Descriptions & RACI Chart

Project Role Descriptions & RACI Chart Project Role Descriptions & RACI (Responsible, Accountable, Consult, & Inform) Chart Executive Summary This document describes the tools used to identify roles and responsibilities for all approved projects.

More information

Project Governance Plan Next Generation 9-1-1 Project Oregon Military Department, Office of Emergency Management, 9-1-1 Program (The OEM 9-1-1)

Project Governance Plan Next Generation 9-1-1 Project Oregon Military Department, Office of Emergency Management, 9-1-1 Program (The OEM 9-1-1) Oregon Military Department, Office of Emergency Management, 9-1-1 Program (The OEM 9-1-1) Date: October 1, 2014 Version: 3.1 DOCUMENT REVISION HISTORY Version Date Changes Updated By 0.1 02/13/014 Initial

More information

The Project Management Knowledge Areas as defined by PMI (PMBOK, 2004)

The Project Management Knowledge Areas as defined by PMI (PMBOK, 2004) The Project Management Knowledge Areas as defined by PMI (PMBOK, 2004) is the processes required to ensure that the various elements of the project are properly coordinated. the processes required to ensure

More information

COMMUNICATIONS MANAGEMENT PLAN

COMMUNICATIONS MANAGEMENT PLAN <PROJECT NAME> COMMUNICATIONS MANAGEMENT PLAN TEMPLATE This Project Communications Management Template is free for you to copy and use on your project and within your organization. We hope that you find this template

More information

Problem Management Fermilab Process and Procedure

Problem Management Fermilab Process and Procedure Management Fermilab Process and Procedure Prepared for: Fermi National Laboratory June 12, 2009 Page 1 of 42 GENERAL Description Purpose Applicable to Supersedes This document establishes a Management

More information

PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE:

PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE: PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE: Project Name Project Management Plan Document Information Document Title Version Author Owner Project Management Plan Amendment History

More information

Department of Administration Portfolio Management System 1.3 June 30, 2010

Department of Administration Portfolio Management System 1.3 June 30, 2010 E 06/ 30/ 2010 EX AM PL 1. 3 06/ 28/ 2010 06/ 24/ 2010 06/ 23/ 2010 06/ 15/ 2010 06/ 18/ 2010 Portfolio System 1.3 June 30, 2010 Contents Section 1. Project Overview... 1 1.1 Project Description... 1 1.2

More information

Health Information Technology Financial Subcommittee

Health Information Technology Financial Subcommittee Health Information Technology Financial Subcommittee Mission The Financial Subcommittee has been created to oversee the operational budget and capital investment planning for Health Information Technology

More information

Voice Over IP Network Solution Design, Testing, Integration and Implementation Program Overview

Voice Over IP Network Solution Design, Testing, Integration and Implementation Program Overview Voice Over IP Network Solution Design, Testing, Integration and Implementation Program Overview 1/1 Table of Contents 1. Introduction...3 2. Executive Summary...4 3. Program Definition...5 3.1. Program

More information

IBAPro Project Management Methodology

IBAPro Project Management Methodology IBAPro Project Management Methodology A description of the IBApps Project Management Methodology and Implementation Process Version 2.2, June 2013 Contents 1. Project Management... 3 2. Phases... 3 2.1.

More information

Client Services Service Level Agreement

Client Services Service Level Agreement RMI Corporation Client Services Service Level Agreement 40 Darling Drive Avon, CT 06001 Phone: 860.677.1005 *Fax: 860.677.2454 RMI Corporation Client Services - Service Level Agreement TABLE OF CONTENTS

More information

UNIVERSITY OF GUELPH PROJECT MANAGEMENT FRAMEWORK

UNIVERSITY OF GUELPH PROJECT MANAGEMENT FRAMEWORK UNIVERSITY OF GUELPH PROJECT MANAGEMENT FRAMEWORK Table of Contents Document Purpose:... 3 What is a Project?... 3 What is not a Project? (e.g. Operational Tasks)... 3 What is Project Management?... 4

More information

Issue Management Plan Preparation Guidelines

Issue Management Plan Preparation Guidelines Issue Management Plan Preparation Guidelines TABLE OF CONTENTS 1. Purpose of Document 1 2. Definition of Issue Management 1 3. Objectives of Issue Management 1 4. Terms, Acronyms and Abbreviations 1 5.

More information

ETC HELPDESK POLICY. 1. Policy Title. ETC Helpdesk Policy. 2. Policy Number SCT-AD-005-V2. 3. Purpose

ETC HELPDESK POLICY. 1. Policy Title. ETC Helpdesk Policy. 2. Policy Number SCT-AD-005-V2. 3. Purpose ETC HELPDESK POLICY 1. Policy Title ETC Helpdesk Policy 2. Policy Number SCT-AD-005-V2 3. Purpose The purpose of this policy is to provide a system that will give an effective technical Helpdesk service

More information

Contents. Service Request Departmental Procedures

Contents. Service Request Departmental Procedures Departmental Procedures Contents Process... 2 Scope... 2 Key Definitions... 2 Metrics and Reporting... 2 Roles and Responsibilities... 3 Level Agreements... 3 RACI Chart... 4 Process Flow and Procedure...

More information

Post-Implementation Review

Post-Implementation Review Table of Contents 1. Post Implementation Review ()... 1 1.1. What is a Post Implementation Review?...1 1.2. Why is the Used?... 1 1.3. Where does a fit in?... 2 1.4. What constitutes the process?... 2

More information

ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES

ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES 1. ROLE DEFINITIONS ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES The purpose of this section is to distinguish among the roles interacting with the SPM obtained through

More information

Version Prepared by: Approved by: Approved by: My signature indicates approval of this Change Management Plan.

Version <Type Version #> Prepared by: Approved by: Approved by: My signature indicates approval of this Change Management Plan. CHANGE MANAGEMENT PLAN Version My signature indicates approval of this Change Management Plan. Prepared by: Approved by: Approved by: Project Manager Agency CIO Project

More information

Project Knowledge Areas

Project Knowledge Areas From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.

More information

Enter Project Name Project Management Plan (PMP) Kickoff Month, Day, Year

Enter Project Name Project Management Plan (PMP) Kickoff Month, Day, Year Enter Project Name Project Management Plan (PMP) Kickoff Month, Day, Year 1 Purpose The Project Management Plan (PMP) is a formal, approved document used to manage project execution. The PMP documents

More information

Cisco Change Management: Best Practices White Paper

Cisco Change Management: Best Practices White Paper Table of Contents Change Management: Best Practices White Paper...1 Introduction...1 Critical Steps for Creating a Change Management Process...1 Planning for Change...1 Managing Change...1 High Level Process

More information

Project Management for Everyone

Project Management for Everyone Project Management for Everyone Contact Information Adam Donaldson, PMP Business Management & Analysis Group System, Analytics & Insights Group Phone: (202) 994-6867 Email: adonald@gwu.edu Objectives Basic

More information

Tel: Fax: [Project Name] [Sub-Project, phase, etc.]

Tel: Fax: [Project Name] [Sub-Project, phase, etc.] [Company Name] [Company Address] Tel: Fax: [Company Phone] [Company Fax] [Company E-mail] [Ref. number] [Author] Change Management Plan [Sub-Project, phase, etc.] The project change management plan is

More information

To provide a procedure and associated guidelines to facilitate the management of project dependencies.

To provide a procedure and associated guidelines to facilitate the management of project dependencies. Management DEPENDENCY MANAGEMENT Purpose To provide a procedure and associated guidelines to facilitate the management of project dependencies. Overview Dependencies in this Phase are defined as actions,

More information

ACESS A Comprehensive Enterprise Social Services System

ACESS A Comprehensive Enterprise Social Services System State of Louisiana Department of Social Services ACESS A Comprehensive Enterprise Social Services System Scope and Change Management Plan Deliverable AC07 APRIL 27, 2005 VERSION 2.0 State of Louisiana

More information

Control Number: Title: Contract Management: Healthcare Services

Control Number: Title: Contract Management: Healthcare Services Idaho Department of Correction Stard Operating Procedure Control Number: 1 of 16 Adopted: 5-20-2011 Reviewed: 6-8-2011 Next Review: 6-8-2013 Management Division General Administration Management: Healthcare

More information

Crosswalk Between Current and New PMP Task Classifications

Crosswalk Between Current and New PMP Task Classifications Crosswalk Between Current and New PMP Task Classifications Domain 01 Initiating the Project Conduct project selection methods (e.g., cost benefit analysis, selection criteria) through meetings with the

More information

Process Description Incident/Request. HUIT Process Description v6.docx February 12, 2013 Version 6

Process Description Incident/Request. HUIT Process Description v6.docx February 12, 2013 Version 6 Process Description Incident/Request HUIT Process Description v6.docx February 12, 2013 Version 6 Document Change Control Version # Date of Issue Author(s) Brief Description 1.0 1/21/2013 J.Worthington

More information

- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B0400021

- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B0400021 - ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B0400021 About this document this is a detailed description of typical Project Manager (PM) duties, responsibilities, and

More information

Risk/Issue Management Plan

Risk/Issue Management Plan Risk/Issue Management Plan Centralized Revenue Opportunity System November 2014 Version 2.0 This page intentionally left blank Table of Contents 1. Overview... 3 1.1 Purpose... 3 1.2 Scope... 3 2. Roles

More information

ACESS A Comprehensive Enterprise Social Services System

ACESS A Comprehensive Enterprise Social Services System State of Louisiana Department of Social Services ACESS A Comprehensive Enterprise Social Services System Project Control Standards and Procedures Deliverable AC09 SEPTEMBER 1, 2004 VERSION 1.1 State of

More information

IT Service Provider and Consumer Support Engineer Position Description

IT Service Provider and Consumer Support Engineer Position Description Engineer Position Description February 9, 2015 Engineer Position Description February 9, 2015 Page i Table of Contents General Characteristics... 1 Career Path... 2 Explanation of Proficiency Level Definitions...

More information

Project Manager Job Descriptions

Project Manager Job Descriptions Promotion Criteria Position Overview Statement Principal Duties and Responsibilities PROJECT MANAGER Admin Level 4 Typically >8 years in increasing responsible IT leadership role; typically managed one

More information

ITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE

ITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE PROJECT MANAGEMENT GUIDELINE SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE Table of Contents Introduction... 3 Project Execution and Control Phase Overview... 3 Activities and Documents in the Execution

More information

Business Analyst Position Description

Business Analyst Position Description Analyst Position Description September 4, 2015 Analysis Position Description September 4, 2015 Page i Table of Contents General Characteristics... 1 Career Path... 2 Explanation of Proficiency Level Definitions...

More information

PHASE 8: IMPLEMENTATION PHASE

PHASE 8: IMPLEMENTATION PHASE PHASE 8: IMPLEMENTATION PHASE The Implementation Phase has one key activity: deploying the new system in its target environment. Supporting actions include training end-users and preparing to turn the

More information

POLICY AND PROCEDURES OFFICE OF STRATEGIC PROGRAMS. CDER Informatics Governance Process. Table of Contents

POLICY AND PROCEDURES OFFICE OF STRATEGIC PROGRAMS. CDER Informatics Governance Process. Table of Contents CENTER FOR DRUG EVALUATION AND RESEARCH MAPP 7600.8 Rev. 1 POLICY AND PROCEDURES OFFICE OF STRATEGIC PROGRAMS CDER Informatics Governance Process Table of Contents PURPOSE...1 BACKGROUND...1 POLICY...2

More information

ITSM Process Description

ITSM Process Description ITSM Process Description Office of Information Technology Incident Management 1 Table of Contents Table of Contents 1. Introduction 2. Incident Management Goals, Objectives, CSFs and KPIs 3. Incident Management

More information

hi Information Technologies Change Management Standard

hi Information Technologies Change Management Standard hi Information Technologies Change Management Standard Classification Service Delivery Standard # SVD-002 Approval Authority Chief Information Officer Implementation Authority Director, Service Delivery

More information

Contract and Vendor Management Guide

Contract and Vendor Management Guide Contents 1. Guidelines for managing contracts and vendors... 2 1.1. Purpose and scope... 2 1.2. Introduction... 2 2. Contract and Vendor Management 2.1. Levels of management/segmentation... 3 2.2. Supplier

More information

I. Creating a Project Request in TeamDynamix: Defining

I. Creating a Project Request in TeamDynamix: Defining I. Creating a Project Request in TeamDynamix: Defining Project Request Site: https://projects.xavier.edu/tdclient/login.aspx This section will describe the details to create a project request. A project

More information

Information Technology Project Oversight Framework

Information Technology Project Oversight Framework i This Page Intentionally Left Blank i Table of Contents SECTION 1: INTRODUCTION AND OVERVIEW...1 SECTION 2: PROJECT CLASSIFICATION FOR OVERSIGHT...7 SECTION 3: DEPARTMENT PROJECT MANAGEMENT REQUIREMENTS...11

More information

Subject Area 1 Project Initiation and Management

Subject Area 1 Project Initiation and Management DRII/BCI Professional Practice Narrative: Establish the need for a Business Continuity Plan (BCP), including obtaining management support and organizing and managing the BCP project to completion. (This

More information

Service Level Agreement for Database Hosting Services

Service Level Agreement for Database Hosting Services Service Level Agreement for Database Hosting Services Objective Global Service Levels include the general areas of support that are applicable to every ITS service. The purpose of the Service Level Agreement

More information

Corrective and Preventive Action Process

Corrective and Preventive Action Process GT001, rev. 2 Document # GOP210 Release Date: 18-aug-2013 Page 1 of 6 Purpose The purpose of this document is to describe the process for handling actual and potential non-conformances to the certification

More information

OE PROJECT CHARTER TEMPLATE

OE PROJECT CHARTER TEMPLATE PROJECT : PREPARED BY: DATE (MM/DD/YYYY): Project Name Typically the Project Manager Project Charter Last Modified Date PROJECT CHARTER VERSION HISTORY VERSION DATE (MM/DD/YYYY) COMMENTS (DRAFT, SIGNED,

More information

IT Services. Service Level Agreement

IT Services. Service Level Agreement IT Services Service Level Agreement Contents 1 Purpose... 3 2 IT Services Objectives... 3 3 IT Helpdesk... 3 3.1 Issues... 3 3.2 Service Requests... 4 3.3 Development Requests... 4 4 Priorities... 4 5

More information

Job Description. Job Title: Department: ICT Service Support Manager Responsible to:

Job Description. Job Title: Department: ICT Service Support Manager Responsible to: Job Description Job Title: ICT Service Support Manager Responsible to: ICT/IS Manager Main purpose of the job: Department: INFORMATION TECHNOLOGY Number of people directly managed: 3 + temporary contractors

More information

Why are PMO s are Needed on Large Projects?

Why are PMO s are Needed on Large Projects? Why are PMO s are Needed on Large Projects? Keeps Project Manager focused on: Priority risks Priority issues Stakeholder alignment Technical challenges Ensures administrative tasks are completed: Projects

More information

Final Report on Project Management Skills of the University of California Libraries Staff. July, 2010

Final Report on Project Management Skills of the University of California Libraries Staff. July, 2010 Final Report on Project Management Skills of the University of California Libraries Staff July, 2010 from the Project Management Skills Task Force Members: Joan Starr, CDL, Chair Mary Linn Bergstrom, UC

More information

PMP Examination Tasks Puzzle game

PMP Examination Tasks Puzzle game PMP Examination Tasks Puzzle game Here is a great game to play to test your knowledge of the tasks you will be tested on in the actual examination. What we have done is take each of the domain tasks in

More information

INTERNAL SERVICES GROUP PMO

INTERNAL SERVICES GROUP PMO Ownership & Awareness Program 1 Program 3 Program 4 Program 5 Program 6 Program 7 Program 2 Cap ability Development Infra structure Program n INTERNAL SERVICES GROUP ESSENTIAL FUNCTIONS Act as an interface

More information

Project Start Up. Start-Up Check List. Why a Project Check List? What is a Project Check List? Initial Release 1.0 Date: January 1997

Project Start Up. Start-Up Check List. Why a Project Check List? What is a Project Check List? Initial Release 1.0 Date: January 1997 Why a Project Check List? A good way to ensure that all start-up tasks are completed prior to actually starting the project is to develop a start-up check list. The check list can be developed and then

More information

CHANGE MANAGEMENT CHARTER. Client Services Information Technology Services. Author: Rod Walker Version: 1.0. Change Management Charter

CHANGE MANAGEMENT CHARTER. Client Services Information Technology Services. Author: Rod Walker Version: 1.0. Change Management Charter CHANGE MANAGEMENT CHARTER Client Services Information Technology Services Author: Rod Walker Version: 1.0 Document Change History Version Date Changed By Modifications 0.1 19/02/2013 Rod Walker Initial

More information

Project Implementation Plan

<Project Name> Project Implementation Plan Client Logo Project Implementation Plan Version 0.1 Prepared By: David Bowman Information Management Architect Table of Contents Revision History...4 1. INTRODUCTION...5 1.1. Purpose...5

More information

Who Should be on Your Project Team: The Importance of Project Roles and Responsibilities

Who Should be on Your Project Team: The Importance of Project Roles and Responsibilities Who Should be on Your Project Team: The Importance of Project s and One significant factor contributing to the success of projects is having the right people engaged in the process. Who are the right stakeholders

More information

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project:

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Project Audit & Review Checklist The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Relevance (at this time) Theory & Practice (How relevant is this attribute

More information

Information Technology Governance Overview and Charter

Information Technology Governance Overview and Charter Information Technology Governance Overview and Charter Prepared by: Project #: Date submitted Document version: IT Governance Charter v03.05.2012 1.0 48.0 - Page 1 of 34 Document History Version Date Author

More information

Chapter 12 Contract Management. Administrative Process Related to Award Chapter 9

Chapter 12 Contract Management. Administrative Process Related to Award Chapter 9 Chapter 12 Management Solicitation Development Chatper 6 Administrative Process Related to the Solicitation Chapter 7 Evaluation and Award Chapter 8 Administrative Process Related to Award Chapter 9 ing

More information

Commonwealth of Massachusetts IT Consolidation Phase 2. ITIL Process Flows

Commonwealth of Massachusetts IT Consolidation Phase 2. ITIL Process Flows Commonwealth of Massachusetts IT Consolidation Phase 2 ITIL Process Flows August 25, 2009 SERVICE DESK STRUCTURE Service Desk: A Service Desk is a functional unit made up of a dedicated number of staff

More information

Project Management Guidelines

Project Management Guidelines Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW.

More information

Title: DISASTER RECOVERY/ MAJOR OUTAGE COMMUNICATION PLAN

Title: DISASTER RECOVERY/ MAJOR OUTAGE COMMUNICATION PLAN POLICY: This policy is intended to address organizational wide communication executed during a or major IS service outage. When a disaster occurs or when any critical system/infrastructure component is

More information

Maturity Model. March 2006. Version 1.0. P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce

Maturity Model. March 2006. Version 1.0. P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce Maturity Model March 2006 Version 1.0 P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce This is a Value Added product which is outside the scope of the HMSO

More information

Input, Output and Tools of all Processes

Input, Output and Tools of all Processes 1 CIS12-3 IT Project Management Input, Output and Tools of all Processes Marc Conrad D104 (Park Square Building) Marc.Conrad@luton.ac.uk 26/02/2013 18:22:06 Marc Conrad - University of Luton 1 2 Mgmt /

More information

State of Washington. BHAS Help Desk Support Services. July 2015 V1.0

State of Washington. BHAS Help Desk Support Services. July 2015 V1.0 State of Washington BHAS Help Desk Support Services July 2015 V1.0 WA-Behavioral Health Assessment Solution (BHAS ) BHAS supports the Child and Adolescent Needs and Strengths Assessment (CANS) and Adult

More information

Following up recommendations/management actions

Following up recommendations/management actions 09 May 2016 Following up recommendations/management actions Chartered Institute of Internal Auditors At the conclusion of an audit, findings and proposed recommendations are discussed with management and

More information

RDTL Procurement Best Practice Guide 7: Managing Contracts. RDTL MINISTRY OF FINANCE Procurement Service BEST PRACTICE GUIDE 7: MANAGING CONTRACTS

RDTL Procurement Best Practice Guide 7: Managing Contracts. RDTL MINISTRY OF FINANCE Procurement Service BEST PRACTICE GUIDE 7: MANAGING CONTRACTS RDTL MINISTRY OF FINANCE Procurement Service BEST PRACTICE GUIDE 7: MANAGING CONTRACTS 1 RDTL Procurement Guidelines The Procurement Legal Regime Decree Law sets out new procurement processes which must

More information

PRINCIPLES: The following principles underpin the feedback management system and will be reflected in feedback management procedures at all levels:

PRINCIPLES: The following principles underpin the feedback management system and will be reflected in feedback management procedures at all levels: Approved by: of Directors Effective Date: May 7, 2013 No. B-22 Issued by: Administration Review Date: May 7, 2013 Department(s) All Version: 2 Archived: Y POLICY: The of Directors recognizes that patient

More information

Customer Support Policy

Customer Support Policy Customer Support Policy This Customer Support Policy ( Policy ) describes the Support that Invenias provides to Customers that have paid all applicable fees and that are using Licensed Software in a Supported

More information

7.11a: Quality in Project Management: PRINCE2 and ISO 9000

7.11a: Quality in Project Management: PRINCE2 and ISO 9000 7.11a: Quality in Project Management: PRINCE2 and ISO 9000 An overview of the PRINCE2 Method (PRINCE2 is a Trade Mark of the Office of Government Commerce) by Peter Whitelaw, Rational Management Pty Ltd,

More information

Enterprise Architecture Governance Plan Phase 1 Report

Enterprise Architecture Governance Plan Phase 1 Report Enterprise Architecture Governance Plan Phase 1 Report Enterprise Architecture Governance Plan Report and Recommendations for the Smarter Balanced Assessment Consortium 20 January 2012 2 Smarter Balanced

More information

CCIT Change Management Procedures & Documentation

CCIT Change Management Procedures & Documentation CCIT Change Management Procedures & Documentation 1.0 Introduction A major challenge within any organization is the ability to manage change. This process is even more difficult within an IT organization.

More information

MNLARS Project Audit Checklist

MNLARS Project Audit Checklist Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?

More information

RFP Attachment C Classifications

RFP Attachment C Classifications RFP 1. Applications IT Architect Analyzes and designs the architecture for software applications and enhancements, including the appropriate application of frameworks and design patterns and the interrelationships

More information

Department of Planning, Transport and Infrastructure JOB AND PERSON SPECIFICATION

Department of Planning, Transport and Infrastructure JOB AND PERSON SPECIFICATION Department of Planning, Transport and Infrastructure JOB AND PERSON SPECIFICATION Title of Position: Senior Project Manager Directorate: Public Transport Services Classification Code: ASO7 Branch/Section:

More information

[name of project] Service Level Agreement

[name of project] Service Level Agreement [name of project] Service Level Agreement Policies and Procedures Posting: Nov.2008 Rev# xxx CIO Sign-Off: Approved and Reviewed By: Date: Document ID: SLA Revision 001 Authors: Disclaimer: Document sign-off

More information

Software Project Management Plan

<name of project> Software Project Management Plan The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor

More information

CAT-MIS Project Management

CAT-MIS Project Management CAT-MIS Project Management Communicat Accounting Transition to Management Information System Project Management Communicat utilises our proven CAT-MIS Project Management method for the implementation of

More information

Project Lifecycle Management (PLM)

Project Lifecycle Management (PLM) Project Lifecycle Management (PLM) Process or Tool? Why PLM? Project Definition Project Management NEW REQUEST/ INITIATIVES SUPPORT (Quick fixes) PROJECT (Start Finish) ONGOING WORK (Continuous) ENHANCEMENTS

More information

Resource Management. Determining and managing the people resources on projects can be complex as:

Resource Management. Determining and managing the people resources on projects can be complex as: Baseline Resource Management RESOURCE MANAGEMENT Purpose To provide a procedure and associated guidelines to facilitate the management of project people resources. Overview This Phase is used to establish

More information

ITIL Example change management procedure

ITIL Example change management procedure ITIL Example change management procedure An example change process diagram Change Intiators outside IT (users/customers/supplier/etc.) Change Initiators IT SERVICE DESK Filters change requests RFC REJECT

More information

Project Management for econnectivity

Project Management for econnectivity Project Management for econnectivity Marilyn Hunter - PMP November 10, 2015 2 Purpose of this session Provide information and understanding of how to lead connectivity projects within AgGateway or within

More information

In accordance with risk management best practices, below describes the standard process for enterprise risk management (ERM), including:

In accordance with risk management best practices, below describes the standard process for enterprise risk management (ERM), including: Enterprise Risk Management Process and Procedures Scope In accordance with risk management best practices, below describes the standard process for enterprise risk management (ERM), including: Risk identification

More information

SCHEDULE K - GOVERNANCE

SCHEDULE K - GOVERNANCE SCHEDULE K - GOVERNANCE 1. PURPOSE AND GUIDING PRINCIPLES 1.1 Purpose This Schedule K sets forth the governance channel, processes and procedures for the effective implementation and management, both strategically

More information

Georgia College & State University

Georgia College & State University Georgia College & State University Milledgeville, GA Change Management Control Procedures 1 Change Management Control Table of Contents TABLE OF REVISIONS... 3 SECTION 1: INTRODUCTION... 4 1.1 Scope and

More information

PHASE 9: OPERATIONS AND MAINTENANCE PHASE

PHASE 9: OPERATIONS AND MAINTENANCE PHASE PHASE 9: OPERATIONS AND MAINTENANCE PHASE During the Operations and Maintenance Phase, the information system s availability and performance in executing the work for which it was designed is maintained.

More information

General Notes Time allowed 1 hour. Answer all 60 multiple choice questions Use the proforma answer sheet provided.

General Notes Time allowed 1 hour. Answer all 60 multiple choice questions Use the proforma answer sheet provided. Introductory Certificate The APM Project Fundamentals Qualification. Examination paper Candidate Number Date Location Examination Paper Sample Paper v1.4 General Notes Time allowed 1 hour. Answer all 60

More information

STANDARD OPERATING PROCEDURE NO. CM.13-00 - 00

STANDARD OPERATING PROCEDURE NO. CM.13-00 - 00 STANDARD OPERATING PROCEDURE NO. CM.13-00 - 00 Version date: Effective Date: Replaces SOP No.: 1 5 January 20 13 15 February 20 13 Approved by: Date No: CM.13 00 00 Effective Date: 15 February 2013 Version

More information

Facilities Portfolio Management Tool

Facilities Portfolio Management Tool 2016 Facilities Portfolio Management Tool Project Charter Budget- Facilities Oversight Office of Financial Management 4/10/2016 CONTENTS Overview... 2 Purpose Statement... 2 Background... 2 Goals & Objectives...

More information

Optum Practice Management & Physician EMR Defect Process Standard Operating Procedure

Optum Practice Management & Physician EMR Defect Process Standard Operating Procedure ptum Practice Management & Physician EMR Defect Process Standard perating Procedure ptum 70 Royal Little Drive Providence, RI 02904 Copyright 2002-2012 ptum. All rights reserved. Document Information Author(s)

More information

Project Management Office (PMO) Charter

Project Management Office (PMO) Charter Project Management Office (PMO) Charter Information & Communication Technologies 10 January 2008 Information & Communication Technologies Enterprise Application DISCLAIMER Services Project Management Office

More information

WVU. PROJECT MANAGEMENT LITE Training Manual for Project Managers and Team Members. Robert C. Byrd Health Sciences Center Chancellor s Office

WVU. PROJECT MANAGEMENT LITE Training Manual for Project Managers and Team Members. Robert C. Byrd Health Sciences Center Chancellor s Office WVU Robert C. Byrd Health Sciences Center Chancellor s Office PROJECT MANAGEMENT LITE Training Manual for Project Managers and Team Members Fostering a culture of high purpose, accountability & accomplishment

More information

ISSC OPERATING PROCEDURES

ISSC OPERATING PROCEDURES ISSC OPERATING PROCEDURES Version 2.0 May 2014 Author: Susan Nesrallah, Sr. Program Coordinator, Management Office, CCS This Document outlines the procedures and processes for the efficient management

More information

Project Management Professional (PMP) Examination Content Outline

Project Management Professional (PMP) Examination Content Outline Project Management Professional (PMP) Examination Content Outline Project Management Institute Project Management Professional (PMP) Examination Content Outline June 2015 Published by: Project Management

More information

means the charges applied by Ancar B Technologies Limited which recur annually;

means the charges applied by Ancar B Technologies Limited which recur annually; This Service Schedule is supplemental to the Master Service Agreement Net-L1-3. CONTENTS Schedule 1 - DEFINITIONS... 1 Schedule 2 - MANAGED INTERNET ACCESS SERVICE PRODUCT INFORMATION... 3 1 MANAGED INTERNET

More information

Service Level Management

Service Level Management Process Guide Service Level Management Company ABC Service Improvement Program (SIP) Process Guide Service Level Management Table of Contents Document Information... 3 Approval... 4 Section 1: Process

More information

CM00 Change Management High Level

CM00 Change Management High Level CM00 Change Management High Level CM01 Create Change CM09 Assess and Execute Emergency / CM03 Approve Change CM05 Implement Change CM02 Assess And Schedule Change CM07 Review Change CM04 Communicate Scheduled

More information

Problem Management ITIL v3 Problem Management Process

Problem Management ITIL v3 Problem Management Process ITIL v3 Process...root cause analysis Content Key definitions Purpose and Objectives Opening problem scenarios Scope Value to business Problem models Reactive and proactive problem management Process Workflow

More information