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

Thornbury Distribution: engagement facts
FieldDetail
ClientThornbury Distribution, 520 employees
IndustryWholesale food distribution
Client and delivery locationsBristol, UK / Lisbon
ProductBusiness Central 22, cloud, moving to BC 24
Roles1 BC AL developer (full-time), 1 BC functional consultant (3 days/week)
Engagement dates5 Feb – 30 Aug 2024
Overlap7 hours GMT
Reporting lineClient 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

Thornbury Distribution: decision rights
DecisionOwner
Ticket priorityClient Service Delivery Manager
Fix acceptanceClient Finance Manager
Code reviewClient senior developer
Release authorisationClient 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.

Thornbury Distribution: work delivered
RoleAssignmentAccepted outputReviewerApprover
AL developerDefect backlog: posting, integration, permissions94 defects closed in the assigned workstreamClient senior developerFinance Manager
AL developerBC 24 update regression142-scenario regression suite; 6 issues raised with MicrosoftClient senior developerService Delivery Manager
Functional consultantClose checklist and reporting fixes11 configuration changes; revised close checklistClient senior developerFinance 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.

Thornbury Distribution: outcomes
MeasureBaselineResultWindowSource
Median defect resolution time11 working days3 working daysApr–Aug 2024Client Jira service board
Open defect backlog1307 (with workarounds)Aug 2024Client Jira
BC 24 update regression—142 of 142 scenarios passedAug 2024Client test record
Update release accepted—12 Aug 2024—Deployment record
First accepted fix—4 business daysFeb 2024Client Jira ticket

Client perspective

“They joined our queue, not their own. Our Finance Manager signs every posting fix, and she signed 94 of them.”

Gary Whitlock, Service Delivery Manager

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.