A delivery process adopted as the group standard
Quality assurance of a Microsoft partner's programme. The delivery process built to demonstrate a better way was adopted as the group standard.
What happened
The engagement was quality assurance of a programme being delivered by a Microsoft partner.
As part of it, a delivery process was built as a demonstration of how the work could be done. The group adopted that process as its standard.
Why it matters
Reviewing someone else’s delivery is easy to do badly: a list of faults and nothing to put in their place. Building a working alternative is a different kind of answer. People can see it run, and can choose to adopt it, as this group did.
The kind of work this is
This is what we mean by delivery put right: the environments, pipelines, branching, testing and release process that a Dynamics 365 or Power Platform team works within.
Pipelines and environments for teams in five countries
Advice on pipelines and environments for a transformation programme with teams in five countries, inside strict data-protection rules.
Manual deployments replaced, and a lost-property app that sorts itself
Manual deployments were replaced, and a lost-property app was built that uses machine learning to categorise what is handed in.
Start with a delivery health check.
One to two weeks on your Dynamics 365 or Power Platform estate, ending in a written report and a costed plan.