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.
What happened
A transformation programme at a global bank had teams in five countries. The engagement was to advise on its pipelines and environments, within strict data-protection rules.
Why it matters
Environments and pipelines decide how a large programme feels to work in. Get them right and teams in different countries can build in parallel and release together. Get them wrong and they wait on each other.
Data protection makes it harder. In a bank, where data may sit and who may see it are settled questions, and the environments have to respect the answers.
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.
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.
Asked back for a fixed-price extension
A fixed-price extension of a system built the year before. Repeat business on work already delivered.
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.