Delivery recovery before UAT
- Type
- Demonstration project
- Project
- IT consulting demonstration project
- Industry
- IT consulting
The scenario and numbers in this demonstration project are simulated data.
- Industry
- IT consulting and contract software delivery
- What was built
- Agents, skills, semantic models and write tools, built on demonstration data
- Where the knowledge came from
- The UAT entry criteria and the client's escalation email, plus demonstration data from the CRM, PSA, ALM and HR systems
Project risk and escalation
- A fixed-price project to replace a bank's core system is three weeks from UAT entry. Defect fixes cannot keep up with new defects, and the key batch conversion module waits for the client's interface specification.
- At firms like this, the PM used to escalate at the weekly meeting, the delivery director then set up a call with the client, and the plan was agreed only the next week.
Entry criteria and project data
- The UAT entry criteria and the client's escalation email are in the Drive. The agent reads both, confirms how the entry criteria are defined and confirms that the specification delay is on the client's side.
- The agent uses semantic models to check defects in ALM, plans and hours in PSA, and staff and availability in HR.
Plan, staffing and scope
- The delivery director asks in Sindri: "Which work on this project can move earlier or run in parallel to win the time back?"
- The agent uses the defect burndown skill to work out how fast defects are fixed and added. The agent works back that fixes must go up and new defects must go down together to meet the criteria before the entry date.
- The agent uses the critical path replan skill to move tasks that can run in parallel ahead while batch conversion is blocked. After the specification arrives, batch conversion is delivered in two parts.
- The agent uses the staffing match skill to scan HR, finds a senior back-end engineer on the bench and borrows staff from another project.
- The agent uses the descope plan skill to defer P3 requirements to phase 2 and freeze non-critical changes until after UAT.
- Sindri gathers the burndown estimate, the replanned critical path, the staffing plan, the deferred requirements and the draft client reply into one decision pack.
- Before the plan revision, the staff reassignment, the scope change addendum and the client reply are written back to PSA, HR and CRM, the agent stops for the delivery director's approval.
Get started
Book a two-hour workshop
AI feasibility review of a live workflow