Customer case study
Business Central Support and Update Testing at Thornbury Distribution
Engagement summary
Thornbury Distribution added a full-time Business Central AL developer and a functional consultant working three days a week from MS Dynamics Guys to its live support team from February to August 2024. The client accepted the Business Central 24 release on 12 August after 142 regression scenarios passed. Its Jira service board recorded median defect resolution time falling from 11 to 3 working days.
Engagement Facts
| Field | Detail |
|---|---|
| Client | Thornbury Distribution, 520 employees |
| Industry | Wholesale food distribution |
| Client and delivery locations | Bristol, UK / Lisbon |
| Product | Business Central 22, cloud, moving to BC 24 |
| Roles | 1 BC AL developer (full-time), 1 BC functional consultant (3 days/week) |
| Engagement dates | 5 Feb – 30 Aug 2024 |
| Overlap | 7 hours GMT |
| Reporting line | Client Service Delivery Manager |
Why the Client Added Capacity
Thornbury distributes food wholesale from Bristol. Its two-person Business Central team was committed to a warehouse integration when its posting and integration backlog reached 130 defects. The August Business Central 24 update created a second need for regression testing while the team continued to support live operations.
Decision Rights
| Decision | Owner |
|---|---|
| Ticket priority | Client Service Delivery Manager |
| Fix acceptance | Client Finance Manager |
| Code review | Client senior developer |
| Release authorisation | Client Service Delivery Manager |
Work Delivered
The AL developer joined Thornbury’s support queue and worked on posting, integration, and permissions defects. The developer also ran the update regression suite and raised six issues with Microsoft. The functional consultant delivered 11 configuration changes and revised the close checklist. Thornbury’s Service Delivery Manager prioritised tickets and authorised releases, its senior developer reviewed changes, and its Finance Manager accepted the support fixes.
| Role | Assignment | Accepted output | Reviewer | Approver |
|---|---|---|---|---|
| AL developer | Defect backlog: posting, integration, permissions | 94 defects closed in the assigned workstream | Client senior developer | Finance Manager |
| AL developer | BC 24 update regression | 142-scenario regression suite; 6 issues raised with Microsoft | Client senior developer | Service Delivery Manager |
| Functional consultant | Close checklist and reporting fixes | 11 configuration changes; revised close checklist | Client senior developer | Finance Manager |
Outcomes
The client’s Jira ticket records the first accepted fix after four business days. Its test and deployment records document the 142 passing scenarios and the release acceptance on 12 August.
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Median defect resolution time | 11 working days | 3 working days | Apr–Aug 2024 | Client Jira service board |
| Open defect backlog | 130 | 7 (with workarounds) | Aug 2024 | Client Jira |
| BC 24 update regression | — | 142 of 142 scenarios passed | Aug 2024 | Client test record |
| Update release accepted | — | 12 Aug 2024 | — | Deployment record |
| First accepted fix | — | 4 business days | Feb 2024 | Client Jira ticket |
Client perspective
“They joined our queue, not their own. Our Finance Manager signs every posting fix, and she signed 94 of them.”
Your next step
Discuss the capacity your team needs
Share the application, workstream and specialist allocation you need. Your team can define its own backlog, acceptance and release responsibilities.