Learning Management System (LMS) Review

Project Charter
The project charter formally authorizes the project to begin, describes the project in further detail, and is the
document of record used as input into the project plan.

Project Name, Scorecard Rating, and SharePoint Link

Planview PPM Pro Project Name Scorecard Rating SharePoint Link
TLT-TLT-Learning Management System Review 80 LMS Review Documents

Project Scope
Scope Section Scope Detail
Business Goal  We are gathering current and future needs for the learning management
system (LMS) from faculty, instructors, learners, staff, and other stakeholders
to understand, at a Purdue system-wide level, the full set of requirements for
such a system. These needs will be used to assess products and make a
recommendation to Dr. Jay Akridge, Provost and Executive Vice President for
Academic Affairs and Diversity, and Dr. Gerry McCartney, Executive Vice
President and Chief Information Officer. Benefits are to provide a robust and
user-friendly experience for faculty, instructors, staff and students at Purdue
for online, residential, credit, non-credit, graduate, and undergraduate
offerings.

Project Objectives  Establish analysis and review task forces

 Capture information and solution proposals against identified requirements
 Communicate with transparency, diligently and widely
 Recommended Solution

High-level  Academic Task Force

Deliverables
 Technology Task Force
 Learning Management System RFP/RFI
 Defined and prioritized requirements
 Big 10 peer review
 Project Plan
 High Level Implementation Strategy
 Communication plan
 Cost\Benefit Analysis of Recommended Solutions(s)
 Recommended Solution(s)
 Develop Use Cases

Project Charter v.3.2 1 of 5 Purdue University ITaP Project Management Office

 Scope Section Scope Detail
High-level  Input opportunity from faculty, staff, students
Requirements
 Transparent and widely distributed communications
 Academic Leadership Support
 System Wide Coordination and Acceptance

Successful  Defined and articulated future system state and needs

Completion Criteria
 A Learning Management System solution(s) is selected and approved for a
system wide implementation
 System wide opportunity for input into the process

Project Benefits
Please Note: Enter what is known at initiation. More benefits may be derived later and recorded in the
closing document.
Who / What Will Measurement
Anticipated Benefits Benefit Measures (The How) Timeframe
Potential cost Benefits University TBD 3-5 Years

Better system for Students & Instructors TBD 3-5 Years

teaching and learning

Increased Usage and Students & Instructors TBD 3-5 Years

Acceptance

High-Level Milestone Schedule

Known Milestones Start Month Target Completion Month
Project Plan June July

Communication Plan June July

Listening Sessions August November

Task Forces’ Investigations August December

RFP Finalization January January

Judged Vendor Responses February March

Vendor Presentations (3) March March

Recommendation March April

Project Charter v.3.2 2 of 5 Purdue University ITaP Project Management Office

Risk(s)
An uncertain event or condition that, if occurs, has a positive or negative effect on a project's objectives.
High-Level Risks Known at Project Initiation
 Poor Communications
 Limited input
 Time Conflicts
 System Wide Acceptance
 Unclear Expectations from Project Plan

Assumptions
Events or circumstances expected to occur during the project life cycle.
High-Level Assumptions as of Project Initiation
 While a single, system-wide solution that will meet the needs of all use cases will be sought and may
be preferable, consideration will be given to the need for multiple solutions.
 Focusing on the best pedagogical choices instead of solely the technical requirements and low-level
feature comparison will result in a better long-term decision that meets the needs of Purdue’s faculty
and students.
 Even if we stay with Blackboard, at some point we will have to migrate from the current offering,
Blackboard Learn, to the new offering, Blackboard Ultra. This will be a major transition and be
comparable to moving to a completely new LMS.
 Regardless of LMS choice, the future product directions of all major vendors are dependent on
software as a service (SaaS), or cloud deployment. If we are to remain current in our use and
support of modern LMSs, we need to evaluate how a SaaS system could be deployed to interact with
Purdue’s current infrastructure.

Constraints
Any events or circumstances that may restrict, limit, or regulate a project.
High-Level Constraints Known at Project Initiation
 Current Contracts
 Time Constraints\Availability
 System Interoperability

Project Charter v.3.2 3 of 5 Purdue University ITaP Project Management Office

Project Budget Information
Item ID Item Name Cost Fund Provider
There are no significant anticipated expenses expected for this project; therefore, there is no project
budget.

Total Cost N\A

Project Sponsors
Executive Sponsors Project Sponsors Project Manager
Jay Akridge Executive Steering Committee Brian York
Gerry McCartney Jenna Rickus, Chair

Project Core Team Members

The core team consists of a wide range of resources with various degrees of time allocations. Below is a
list of major Purdue system wide resources involved in this project.

 Executive Steering Committee

 Academic Taskforce
 Technology Taskforce
 Communications
 Purchasing
 Security

Project Resource Roles Other Than Core Team Members

Project Resources or Roles
 Credit instructors and students
 Non-credit instructors and students
 Face-to-face, hybrid, and online instructors and students
 Instructional and administrative support staff
 Data stewards
 ITaP software commodities group

Project Charter v.3.2 4 of 5 Purdue University ITaP Project Management Office

Approving Authority Signature and Date
Please Note: By approving the Project Charter, you are in agreement with the schedule, scope,
budgeted costs, and the project resources as described herein.
Approval Date
Approving Authority Name and Position Title (via Outlook voting)
Jay Akridge, Provost and Executive Vice President for Academic Monday, August 06, 2018 7:42 AM
Affairs and Diversity

Gerry McCartney, Executive Vice President and CIO Thursday, August 09, 2018 2:47 PM

Jenna Rickus, Associate Vice Provost for Teaching & Learning Sat 7/21/2018 7:35PM

Project Manager
Brian York

Project Charter v.3.2 5 of 5 Purdue University ITaP Project Management Office