Project Scope Statement for CPMIS Implementation at UC Merced, Lecture notes of Business

The project scope for the implementation of digarc's curriculum management system (cpmis) at uc merced. It includes project objectives, in-scope and out-of-scope deliverables, acceptance criteria, constraints, and assumptions. The project aims to align with uc merced’s cloud first strategy, reduce costs and risks, gain efficiencies, and improve user experience.

Typology: Lecture notes

2021/2022

Uploaded on 09/12/2022

shekara_44het
shekara_44het 🇺🇸

4.3

(7)

229 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Project Scope Statement UC Merced IT Project Management Office Page 1 of 4
CPMIS Project Scope Statement
Project Name:
Project Number:
Prepared by: (Project Manager)
Date:
CPMIS
Melissa Tessier
02/07/17
Sponsor:
Business Unit:
Project Type:
Laurie Herbrand / Laura
Martin
Registrar / Senate Office
Standard Complex
Project Scope Statement Document
Description
The Project Scope Statement is the document of record for the project scope. It
expands on the earlier work done in the Project Charter and stablishes a common
understanding of the project scope among project stakeholders. Most important,
it establishes not only what is in scope but also what is out of scope for the
project. As the project progresses, the scope statement may be appended to
reflect scope changes submitted through the Project Change Request process.
Information regarding the business need your project addresses.
Align with UC Merced’s Cloud First Strategy
Retire existing system and move to Digarc’s vendor hosted cloud solution
Cost Reduction & Risk Avoidance
Reduction in manual programming efforts from Engineering to maintain the existing system
Vendor hosted system transfers risk from UCM
Gain Efficiencies
Reduction of manual processes handled by Registrar and other teams that utilize the current
system
Provide a system that can be utilized by all schools existing and in the future
Improved User Experience
User interface is easy to use and supports efficient submission and approval processes
Administrative functionality is available for Registrar and doesn’t require IT programming
Ability to maintain current forms and wokflows by administrative users
Detailed Project Scope
Describe in detail the project deliverables that are included and excluded.
In Scope
pf3
pf4

Partial preview of the text

Download Project Scope Statement for CPMIS Implementation at UC Merced and more Lecture notes Business in PDF only on Docsity!

CPMIS Project Scope Statement

Project Name: Project Number: Prepared by: (Project Manager) Date:

CPMIS Melissa Tessier 02/07/

Sponsor: Business Unit: Project Type:

Laurie Herbrand / Laura

Martin

Registrar / Senate Office ☐^ Standard^ ☒^ Complex

Project Scope Statement Document Description The Project Scope Statement is the document of record for the project scope. It expands on the earlier work done in the Project Charter and stablishes a common understanding of the project scope among project stakeholders. Most important, it establishes not only what is in scope but also what is out of scope for the project. As the project progresses, the scope statement may be appended to reflect scope changes submitted through the Project Change Request process. Project Objective Information regarding the business need your project addresses.

Align with UC Merced’s Cloud First Strategy

• Retire existing system and move to Digarc’s vendor hosted cloud solution

Cost Reduction & Risk Avoidance

• Reduction in manual programming efforts from Engineering to maintain the existing system

• Vendor hosted system transfers risk from UCM

Gain Efficiencies

• Reduction of manual processes handled by Registrar and other teams that utilize the current

system

• Provide a system that can be utilized by all schools existing and in the future

Improved User Experience

• User interface is easy to use and supports efficient submission and approval processes

• Administrative functionality is available for Registrar and doesn’t require IT programming

• Ability to maintain current forms and wokflows by administrative users

Detailed Project Scope Describe in detail the project deliverables that are included and excluded. In Scope

Implementation

  • Implement Digarc Curriculum Management System
  • Build workflows for undergrad and grad that support crosslisted and conjoined paths
  • Create user roles and setup process to automate new users with import from Active Directory
  • Batch Integration with Banner and Acalog
  • Create new reports
  • Training for all required administrative staff and faculty users of the system

Review and Revise Processes

  • Revise approval workflow
  • Update the CRF input form
  • Define reporting criteria and audiences
  • System built to support future Policy updates (deadlines)

Conversion

  • Copy all users from existing system into new system into default role
  • Convert all current finalized/approved Undergrad CRF’s from the existing system into the new system
  • Upload all Grad CRFs from hard copy to the new system in their current state
  • Existing in house solution changed to read only and freeze data
  • Establish archives of old data
  • Communications to Faculty & Staff Out of Scope
  • Library integration for resources
  • Space booking integration
  • Teaching assistance resources
  • Teaching Plan interface
  • U Direct interface
  • Conversion of drafted, incomplete, in process (in workflow) CRFs
  • Definition of new deadlines
  • Book store integration
  • Technology resources
  • Curriculum mapping functionality Project Acceptance Criteria Acceptance criteria are the metrics that must be met before the project services and proposed deliverables will be accepted.
  1. CRF software implementation complete
  2. Workflows are created and support UCM policy
  3. System does not have any critical defects identified during testing
  4. Sample set of CRFs can be submitted and processed through the workflow smoothly and without error (during testing)
  5. Successful conversion and input of data from existing system/format to the new system
  6. Faculty and Staff have been trained on the product Project Constraints A) Cost Describe any cost project limitations that may affect the performance of the project. Example: funding was not planned for in this fiscal year and may delay project start date.
  7. Do not have full confirmation of funding source B) Resource Describe any resource project limitations that may affect the performance of the project. Example: Resources require additional training for project implementation.
  8. Project team resources may be required 10- 20 % during peak times in the project.
  9. Scheduling considerations for faculty involvement. Need to take into account teaching calendar and time off during the off seasons. (Winter, Summer breaks)