Sprint Review 13

SSIS Time Entry Transformation

Sprint 13 Goal (9/10/25 – 9/30/25): Complete Activity Log development work and begin QA functional testing. Design draft records and finalize storage approach. Validate backend APIs (adding blocks on the end points), complete API documentation, and consistent error handling for backend. Continue dev work on auto-populating child participants in the Regarding section, and a system maintenance/communications banner. Pilot with 125 Stearns County users with production data and remediate any reported defects.

Actual Results:

• Activity log development work was completed and QA functional testing started. Some PDM testing began, and some defects are being worked through. All dev items were completed that were assigned for sprint 13.
• Draft version designs were started, drafts will be stored in a table in the web app. Request submitted through SSIS for backend table in 25.4 release. Table exists in dev and QA environments for the web app.
• For the validation of backend APIs, we set up daily automated tests (the only automation at this point is on the service calls). This is only in the QA region so there is no UAT testing. Validation on all endpoints was merged into master; one field of the form submission doesn't have the maximum (because SSIS didn't have it). We still want to add a limitation, but the team will need to set this since there isn't one to follow from SSIS for max number of people in a workgroup. Design needed with Regarding and Contact With sections for maximum number of clients allowed in the list.
• Development merged a story for the consistent error handling piece on the backend and is still working through documentation that continues into sprint 14.
• Auto populate regarding section - Development and some QA work completed, this was an ask by users and is feasible to do, but we brought this to the county-led workgroup with Health Care Administration and they flagged this as a compliance issue. They have asked that only single-client workgroups move forward (one client participant exists in the regarding section and can be checked by the system because there is no one else available to select).
• System Downtime Banner - Backend development completed and some successful testing through email notifications. The software piece that does the changes is done, dev had to make a special endpoint to say the app is down, and once this is merged it should be complete for the backend. Design and front-end development still needed for this with sprint 14.
• Piloted with access granted to 125 Stearns County workers using Production Data and successfully remediated reported defects. Not as many users have piloted the application as expected so more communication and encouragement to onboard users is needed. The TET Product Team emailed users directly to encourage more participation and provided the EHQ survey that we want them to take to continue guiding our efforts.