Customer case study
Microsoft Dynamics 365 Regression and Release Staffing at Kestrel Recruitment Group
Engagement summary
Kestrel Recruitment Group added one full-time QA and release specialist from MS Dynamics Guys for the second phase of its Microsoft Dynamics 365 Customer Service and Power Platform programme. From July to December 2024, the specialist designed and ran regression tests across three releases while Kestrel retained release authority. The client accepted the work on 13 December, and its defect log shows post-release defects fell from 18 to three per release.
Engagement Facts
| Field | Detail |
|---|---|
| Client | Kestrel Recruitment Group (phase two) |
| Industry | Specialist recruitment |
| Client and delivery locations | Leeds, UK / Lisbon |
| Product | Microsoft Dynamics 365 Customer Service, Power Platform |
| Roles | 1 QA and release specialist (full-time) |
| Engagement dates | 1 Jul – 20 Dec 2024 |
| Overlap | 7 hours GMT |
| Reporting line | Client Head of Service Operations |
Why the Client Added Capacity
Phase one had shipped without dedicated QA capacity. Production defects were taking time away from Kestrel's service operations team. The Service Delivery Manager set the regression scope, and the Head of Service Operations owned release decisions.
Decision Rights
| Decision | Owner |
|---|---|
| Regression scope | Client Service Delivery Manager |
| Defect disposition | Client Head of Service Operations |
| Deployment preparation | Specialist executes; client authorises |
| Release authorisation | Client Head of Service Operations |
Work Delivered
The specialist automated 186 regression scenarios and ran three full cycles. They tracked defect dispositions and prepared deployment checklists for each release. Kestrel's technical lead reviewed the work, the Service Delivery Manager accepted regression, and the Head of Service Operations authorised deployment.
| Role | Assignment | Accepted output | Reviewer | Approver |
|---|---|---|---|---|
| QA and release specialist | Regression design and execution | 186 automated regression scenarios; 3 full regression cycles | Client technical lead | Service Delivery Manager |
| QA and release specialist | Defect triage and deployment prep | Defect disposition log across 3 releases; deployment checklists | Client technical lead | Head of Service Operations |
Outcomes
Kestrel's release records show signed regression for all three releases from October through December. Its defect log records 71 issues caught before release during the engagement.
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Post-release defects per release | 18 | 3 | Oct–Dec 2024 | Client defect log |
| Regression scenarios automated | 0 | 186 | Jul–Dec 2024 | Client test management tool |
| Releases delivered with signed regression | 0 of 3 | 3 of 3 | Oct–Dec 2024 | Client release record |
| Defects caught before release | — | 71 | Jul–Dec 2024 | Client defect log |
| First accepted regression cycle | — | 14 business days | Jul 2024 | Client ticket record |
Client perspective
“We stopped finding our own mistakes in production. That's the whole story.”
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.