Customer case study
Microsoft Dynamics 365 Architecture and Technical Staffing at Whitmore Energy
Engagement summary
Whitmore Energy added one full-time technical consultant and a solution architect working two days a week from MS Dynamics Guys to its Microsoft Dynamics 365 programme from January to June 2024. Whitmore accepted the environment and security work on 21 June, including seven approved architecture decisions. Its review log shows six of six releases passing security review from March through June.
Engagement Facts
| Field | Detail |
|---|---|
| Client | Whitmore Energy, 890 employees |
| Industry | Renewable energy |
| Client and delivery locations | Aberdeen, UK / Lisbon |
| Product | Microsoft Dynamics 365 Sales, Customer Service, Dataverse |
| Roles | 1 Technical consultant (full-time), 1 Solution architect (2 days/week) |
| Engagement dates | 8 Jan – 28 Jun 2024 |
| Overlap | 7 hours GMT |
| Reporting line | Client Head of Business Systems |
Why the Client Added Capacity
Whitmore had recurring environment and security issues across Microsoft Dynamics 365 Sales, Customer Service and Dataverse. Two releases had failed security review. Its Head of Business Systems set priorities while its internal engineers retained the build work.
Decision Rights
| Decision | Owner |
|---|---|
| Design decisions | Architect proposes; Enterprise Architect approves |
| Environment strategy | Head of Business Systems |
| Security model | Enterprise Architect |
| Release authorisation | Head of Business Systems |
Work Delivered
The architect documented seven decisions covering environments, security, integration boundaries and the data model, with approval from Whitmore's Enterprise Architect. The technical consultant configured four environments, 14 security roles and integrations under review by the client IT lead. The team also delivered a dependency register that Whitmore used to track open decisions and blockers.
| Role | Assignment | Accepted output | Reviewer | Approver |
|---|---|---|---|---|
| Solution architect | Design decisions | 7 architecture decision records (environment, security, integration boundaries, data model); dependency register | Enterprise Architect | Enterprise Architect |
| Technical consultant | Environment and security configuration | 4 environments; 14 security roles; integration configuration | Client IT lead | Head of Business Systems |
Outcomes
Whitmore's security review log records six passes after two earlier failures. Its architecture decision repository records all seven approvals, and its dependency board shows open blockers declining from 19 to three by June.
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Releases passing security review | 0 of 2 | 6 of 6 | Mar–Jun 2024 | Client security review log |
| Architecture decisions formally recorded | 0 | 7 | Jan–Jun 2024 | Client ADR repository |
| Environment-related incidents | 6 in Q4 2023 | 1 in Q1–Q2 2024 | Jan–Jun 2024 | Client incident log |
| Open blockers in dependency register | 19 | 3 | Jun 2024 | Client dependency board |
| First accepted design decision | — | 10 business days | Jan 2024 | Client ADR record |
Client perspective
“Our Enterprise Architect signs the decisions, and he signed seven. The dependency register is now how we plan.”
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.