User Acceptance Testing

45%

Status

In Process [In Process]

45% complete, updated on Mon 5/18/26 1:09 PM by Jeannette Jasmin Ramos

Changed Percent Complete from 31% to 45%.
UAT is 87% complete with leads reviewing and signing-off the Monday following each sprint. 

Handel is coordinating with users outside of the main functional leads to ensure they have access and familiarity with Banner SaaS Search. 

A student testing session was held on May 6 for initial feedback on FalconNest SaaS with 2 additional session scheduled in June.

Details

Dates
Mon 11/10/25 - Thu 6/4/26
Acct/Dept
Other
Type
Information Technology Projects / Information Technology Projects
Health
Red - At risk with no corrective actions
Program(s)
Created
Wed 12/10/25 4:28 PM
Modified
Mon 5/18/26 1:09 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
Yellow
Schedule Health
Red

Alternate Manager(s)