User Acceptance Testing

26%

Status

In Process [In Process]

26% complete, updated on Tue 3/17/26 4:37 PM by Jeannette Jasmin Ramos

On March 6, Ellucian conducted a demonstration in which they showed progress on capabilities configured/functioning in the SaaS environments (some elements were demonstrated in SaaS TEST and others in SaaS PROD). They also provided Solano with a Smartsheet itemizing the evidence indicators with commentary and links to videos demonstrating various processes. 

Functional leads are reviewing and assessing their progress, and overall, feel that the environment is in state that could support UAT prior to a June 29 go-live provided that Ellucian commit to a high-level of support and dedicate sufficient resources to developing their solutions/configurations.

The Ellucian PM, Dave, informed Jeannette that plans for the next Mock, originally scheduled for March 27,  are still being detailed and he will provide an update by the end of the week. The functional leads agreed that a new Mock would be need to be completed with the environment handed back by April 3 in order to ensure sufficient testing; however, the last 2 mocks required 2-3 weeks. This has been identified as Risk for UAT and the go-live schedule. https://solutions.solano.edu/TDClient/179/Portal/Risks/RiskDet?ID=2553&TID=8330

Details

Dates
Mon 11/10/25 - Fri 5/29/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
Tue 3/17/26 4:37 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

Manager

JR
Jeannette Jasmin Ramos

Alternate Manager(s)

CT
Claudia Tenty