User Acceptance Testing

10%

Status

In Process [In Process]

10% complete, updated on Wed 12/10/25 4:30 PM by Jeannette Jasmin Ramos

Changed Status from New to In Process.
Changed Percent Complete from 0% to 10%.
Changed Health from None - No health has been set to Green - On track.
The project is in the planning phase. Functional areas have identified subject-matter experts for testing. Functional leads have also been tasked with developing test charters and test plans. 

Details

Dates
Mon 11/10/25 - Fri 5/29/26
Acct/Dept
Other
Type
Information Technology Projects / Information Technology Projects
Health
Green - On track
Program(s)
Created
Wed 12/10/25 4:28 PM
Modified
Wed 12/10/25 11:05 PM
Benefit/Purpose
Briefly describe what you hope to achieve by executing the project, including anticipated benefits.
The purpose of the User Acceptance Testing (UAT) workstream is to confirm that the Banner SaaS solution and key integrations support real business processes for staff, faculty, and students before go‑live, and to build user confidence in the new system. UAT also provides a structured way to validate that critical requirements have been met, surface any remaining defects or gaps under realistic scenarios, and ensure that go‑live decisions are based on clear, business‑owned evidence.
Deliverables Requested
List or summarize all specific deliverables resulting from this project. What will the project produce or deliver? These should include items that are specific, measurable, achievable, realistic, and time bound.
(1) A UAT test plan that defines scope, environments, roles, entry/exit criteria, schedule, and sign‑off expectations for each major area (Student, Finance, HR/Payroll, Financial Aid, Research & Planning, Information Services, etc.).​
(2) Business‑focused test scenarios and scripts that reflect real end‑to‑end processes (e.g., registration, census and drops, FA packaging and disbursement, hiring and paying faculty, billing and refunds), with clear expected outcomes.​
(3) Subject-matter group of UAT testers (functional staff and key end users) with UAT instructions, tracking tools, and support channels in place.​
(4) Execution of UAT cycles in the designated SaaS environment, with defects, issues, and change requests logged, prioritized, and tracked to resolution.​
(5) Documented UAT results and formal acceptance/sign‑off from business owners indicating readiness (or clearly defined go‑live conditions and outstanding risks).

Program Review & Participatory Governance

Budget Health
Green
Resource Health
Green
Schedule Health
Green