Information Technology Policy Manual FY22-23

• An initiative from start to finish will typically last less than 30 days. Initiatives may or may not have start and end dates. • Initiatives are typically single tasks that do not require detailed milestone definitions and a host of sub-tasks to perform in order to reach a desired goal.

• Initiatives lack uniqueness and are routinely performed on a daily or weekly basis to support operations. Simply they are not recurring.

• Initiatives apply to maintenance required to support system and application infrastructure.

Maintenance: Routine and preplanned activities used to prolong the life cycle of the product or service. Out of Cycle Change Request: There may be instances where change requests must be routed through following the weekly change management board. These changes were simply not known at the time of the board and cannot wait for the subsequent week. All stakeholders will be provided a copy of the change and time of institution. All stakeholders will have an opportunity to reject the change request as necessary to maintain operations. In such instances the change will be mitigated through the Project Manager and the respective stakeholders. Project : A program management framework that classifies a particular work activity based on enterprise operations. For the purposes of this policy a project consists of the following non-inclusive traits.

• A project from start to finish will last more than 30 days or a month in time.

• A project has a definite start date and a definite end date with defined resources and scope.

• A project should lend itself to having milestones with tasks under each that when completed realizes a significant effort towards your end goal.

• A project will lend itself to have more than a single task but stages where you plan, initiate, and execute to achieve a desired goal.

• A project is a unique effort that is not recurring. ROLES AND RESPONSIBILITIES

The CAB is an empowered body that oversees change procedures, validates, and approves/rejects documented changes. The CAB is responsible for viewing the information provided in every change request in order to ensure that the changes are sufficiently researched, documented, communicated, planned, and executed according to defined cost, schedule, performance, and risk criteria. • The CAB will convene each week to review, approve, or reject pending CRs.

12