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

Whitmore Energy: engagement facts
FieldDetail
ClientWhitmore Energy, 890 employees
IndustryRenewable energy
Client and delivery locationsAberdeen, UK / Lisbon
ProductMicrosoft Dynamics 365 Sales, Customer Service, Dataverse
Roles1 Technical consultant (full-time), 1 Solution architect (2 days/week)
Engagement dates8 Jan – 28 Jun 2024
Overlap7 hours GMT
Reporting lineClient 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

Whitmore Energy: decision rights
DecisionOwner
Design decisionsArchitect proposes; Enterprise Architect approves
Environment strategyHead of Business Systems
Security modelEnterprise Architect
Release authorisationHead 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.

Whitmore Energy: work delivered
RoleAssignmentAccepted outputReviewerApprover
Solution architectDesign decisions7 architecture decision records (environment, security, integration boundaries, data model); dependency registerEnterprise ArchitectEnterprise Architect
Technical consultantEnvironment and security configuration4 environments; 14 security roles; integration configurationClient IT leadHead 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.

Whitmore Energy: outcomes
MeasureBaselineResultWindowSource
Releases passing security review0 of 26 of 6Mar–Jun 2024Client security review log
Architecture decisions formally recorded07Jan–Jun 2024Client ADR repository
Environment-related incidents6 in Q4 20231 in Q1–Q2 2024Jan–Jun 2024Client incident log
Open blockers in dependency register193Jun 2024Client dependency board
First accepted design decision—10 business daysJan 2024Client ADR record

Client perspective

“Our Enterprise Architect signs the decisions, and he signed seven. The dependency register is now how we plan.”

Alan Buchan, Head of Business Systems

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.