Assess a project change: an extra report shortly before go-live
Fictional practice case: a briefing, a change request and the project status become a change assessment for the steering committee.
Situation
A fictional insurance broker is introducing a new system for handling claims. Go-live is planned in five weeks. The sponsor additionally wants an automatic monthly report; the date is to stay.
Source material
«Scope of phase 1: recording and handling claims, interface to the customer master data, training for 25 employees. Reports: the system’s standard reports.»
«For management we need an automatic monthly report by line of business, processing time and open cases from go-live. The date must not move.»
«Status amber. Interface tests one week behind, caused by missing test data. This uses up the one-week time buffer. Training planning on track.»
Task for the AI
Create a change assessment for the steering committee. Separate agreed scope from the new request, set out three options and derive impacts only from the sources. Claim neither feasibility nor costs; flag missing estimates explicitly.
Result: change assessment (draft for the steering committee)
Agreed scope
- Recording and handling, customer master interface, training for 25 employees, standard reports (source 1).
New change request
- Automatic monthly report by line of business, processing time and open cases from go-live, date unchanged (source 2). Not in the agreed scope.
Three options
- Option 1: go-live as planned with standard reports; the monthly report follows as a change after go-live.
- Option 2: add the report before go-live; only conceivable if additional capacity is secured.
- Option 3: examine an interim solution, such as a manual monthly extract from the standard reports, until the report is built.
Known impacts
- The schedule has no buffer left; additional work before go-live hits a project with amber status (source 3).
- Whether the standard reports provide the requested figures is not stated in the sources.
Risks and dependencies
- Option 2 could tie up the same people as the delayed interface tests.
- Processing time requires receipt and closing dates to be recorded reliably.
Missing effort estimates
- Effort and cost of the report: supplier estimate outstanding.
- Effort for the interim solution and additional test time: not estimated.
Decision required
- The steering committee decides which option to pursue and whether date or scope takes priority. The supplier estimate is obtained first.
Sources, assumptions and open information
- Sources
- Project briefing, sponsor’s change request, project status from last week.
- Assumptions
- The status is current. The report would partly need the same specialists as the tests; the project manager confirms this.
- Still open
- Effort, costs, supplier capacity, data quality for processing time.
What people review and decide
The project manager reviews the assessment with the supplier, the steering committee decides. The AI makes no decision and does not declare any option feasible.
Benefit in this situation
The decision rests on documented impacts and named gaps instead of a spontaneous yes under time pressure.
