At risk · flagged 2 weeks running
CRM migration
Owner: Tom Okafor · Go-live: 30 November · Budget: 94% used
Jira shows the project on track, but data mapping has used 128% of its budgeted hours and the integration has had no changes for 11 days. The 30 November go-live is unlikely without a decision this week.
Why it was flagged · 4 sources
Harvest · Data mapping at 128% of budgeted hours186 of 145 hours
| Task | Budget | Used | Over |
|---|---|---|---|
| Legacy contact records | 40 | 71 | +31 |
| Alumni giving history | 35 | 48 | +13 |
| Event attendance | 30 | 34 | +4 |
| Consent records | 40 | 33 | −7 |
Time entries 1–18 October, 9 people. Synced today at 06:30.
GitHub · No integration changes merged for 11 daysLast merge 8 Oct
- PR #214 · Contact sync: map consent fields · opened 8 Oct · awaiting review
- PR #217 · Alumni giving import job · opened 8 Oct · awaiting review
- PR #219 · Retry failed sync batches · opened 8 Oct · awaiting review
3 open pull requests awaiting review on the integration repository. Synced today at 06:30.
SharePoint · Supplier data addendum still unsignedDue 22 Oct
Found in /CRM/Contracts/Data-Processing-Addendum-v3.docx · last edited 2 Oct. No signature block completed.
Jira · 78% of tasks done; team status "On track"96 of 123 tasks
| Area | Done | Open |
|---|---|---|
| Data model and design | 31 | 0 |
| Data mapping | 42 | 6 |
| Integration | 15 | 13 |
| Testing and training | 8 | 8 |
The 27 open tasks include all integration and testing work. Notes on CRM-212 mention duplicate records from a 2019 import.
Status history
- Wk 38On track
- Wk 39On track
- Wk 40On track
- Wk 41On track
- Wk 42At risk
- Wk 43At risk
Recommendation
Escalate the supplier addendum today. At Wednesday's steering group, agree three weeks of extra data-mapping resource (about 60 hours) to hold 30 November, or plan a move to 14 December.
Checked by Sarah Bertorelli · 07:40 today