Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Cloud and platforms

DevOps and platform engineering: an internal platform that serves delivery

Asking every team to master everything, from code to infrastructure, ends up slowing everyone down. Our consultants build with your teams the platform and golden paths that make good practice simpler than the workaround.

Our principles

  • A platform managed as a product, with its users
  • Golden paths that standardise without prohibiting
  • Delivery and adoption indicators tracked over time
In brief

DevOps brings development and operations closer together to deliver more often and more safely; platform engineering is its extension, entrusting a self-service internal platform to a dedicated team. Management Square strengthens your teams to design and put in place the delivery pipeline, infrastructure as code and golden paths that shorten the journey from code to production.

Scope

How we contribute

  1. Delivery flow assessment

    Following a real change, from code commit to production: steps, waits, manual rework, approvals. The assessment measures where time is lost before proposing a tool.

  2. Integration and deployment pipeline

    Build, tests, security scans, production of traceable artefacts and progressive deployment, in a common pipeline that teams can extend.

  3. Infrastructure as code

    Description of the infrastructure in versioned repositories, with a tool such as Terraform: shared modules, review of changes, detection of drift between the code and what actually exists.

  4. Internal developer platform

    Design of the self-service offering: environments, databases, service exposure, secrets management, catalogue and documentation.

  5. Golden paths

    For the most frequent needs, a complete, documented and maintained path, which includes security, observability and cost tagging by default.

  6. Organising the platform team

    Mandate, roles, product owner, relationship with user teams and contribution rules. The team serves the other teams, it does not control them.

Page contents

From DevOps to platform engineering: why the promise stalled

The question of DevOps and platform engineering generally arises after a first phase of adoption. Teams have automated their deployments, learned to describe their infrastructure as code and taken on part of operations. The principle could be summed up in one phrase: whoever builds an application also keeps it running.

At small scale, the model works. At large scale, it produces an unexpected effect. Each team builds its own delivery pipeline, its own modules, its own security settings. Developers spend a growing share of their time on tooling that has nothing specific to their product. Practices diverge, configuration gaps accumulate and a rule change has to be repeated as many times as there are teams.

Platform engineering responds to this burden. A dedicated team provides the others with ready-to-use capabilities. It does not take back responsibility for the applications: it removes from product teams what does not set them apart. Our glossary entry on platform engineering details its definition.

Delivery pipeline, infrastructure as code, platform: who does what

Three building blocks are layered on top of one another. Confusing them leads to buying one in the belief that you are getting all three.

Building block What it provides Who owns it Sign that it works
Integration and deployment pipeline A code change is built, tested, checked and then deployed without any manual action Platform team for the foundation, product teams for their own steps A production release is a routine event
Infrastructure as code Infrastructure is described in versioned files that are reviewed and can be replayed Platform team for the modules, product teams for their use An environment can be recreated identically from the repository
Internal developer platform Common capabilities are offered on a self-service basis, with their rules built in Platform team, with a product owner Teams obtain what they need without opening a request

The delivery pipeline is also where controls are applied: automated tests, dependency analysis, verification of security rules expressed as code. This aspect connects with our software quality offering, which deals with test strategy.

Golden paths: standardising without prohibiting

A golden path is a complete answer to a frequent need: exposing a web service, launching a scheduled job, publishing a programming interface. It brings together a repository template, a preconfigured delivery pipeline, the necessary infrastructure resources, collection of logs and metrics, and documentation.

Its strength lies in a design choice: it is not imposed. A team can depart from it if its need requires, provided it takes responsibility itself for what it builds off the path. This freedom obliges the platform team to make its offering genuinely convenient. A platform that has to be made mandatory in order to be used has a product problem, not a discipline problem.

Our approach: treating the platform as a product

Observing before building. We follow a few real changes from end to end and ask developers what slows them down. The list of irritants identifies the first capabilities to offer.

Delivering a first, complete path. Rather than a broad and unfinished foundation, we recommend aiming for a path usable by a volunteer team, from the first commit to production. This team acts as first customer and first critic.

Establishing a product relationship. The platform has a roadmap, a product owner, documentation, a support channel and versions. Teams’ requests are prioritised according to their frequency, not according to the influence of the requester.

Extending through demand. Each new path meets a need observed in several teams. Contributions from user teams are encouraged and governed.

Operating the platform itself. A platform on which all deliveries depend becomes a critical service. It must have its own reliability objectives, according to the practices described in our SRE and observability offering.

The same logic applies to data science teams, whose model deployment needs are dealt with in our page on MLOps.

The pitfalls of a platform approach

  • Building for assumed users. A platform designed without developers solves its authors’ problems.
  • Starting with the shop window. A polished portal that only triggers manual requests in the background has changed nothing.
  • Renaming the operations team. If the platform team continues to handle requests by hand, the name has changed and nothing else.
  • Leaving infrastructure code without discipline. Changes made by hand in the provider’s console make reality diverge from its description. Without review or drift detection, the code loses its value as a reference.
  • Piling up tools. Each tool added must be operated, updated and documented. A lean, maintained platform is better than an extensive, fragile catalogue.

Measuring delivery and adoption

Two families of indicators complement each other.

The first concerns delivery. Four measures are commonly used: deployment frequency, the time between a code change and its production release, the change failure rate and the time to restore service after a failure. They are often called DORA metrics, after the DORA research programme (dora.dev), which now publishes a fifth: the share of unplanned deployments caused by a production incident. They have nothing to do with the European regulation of the same acronym.

The second concerns adoption of the platform:

  • the share of services that follow a golden path;
  • the time a team needs to release a new service to production for the first time;
  • the time a newcomer needs to deliver their first change;
  • the volume of manual requests still sent to the platform team;
  • developers’ assessment, gathered at regular intervals.

We set with you how each indicator is calculated from the framing stage. A measure whose source changes along the way no longer makes it possible to observe progress.

Typical work

What our consultants contribute to

Delivery flow map

The steps, lead times and blocking points observed on real changes.

Platform roadmap

The capabilities to be offered, ranked by frequency of need and by benefit for the teams.

Documented technical foundation

Delivery pipeline, infrastructure modules and first golden paths, with their user documentation.

Delivery and adoption dashboard

The agreed indicators, how they are calculated and their source.

See also

Related services

Software quality and testing Testing more is not enough: you need to test what matters, at the right level and at the right time. Our consultants help your teams build a risk-based test strategy and automated controls that make every production release more predictable. Custom software development A custom application is justified when it embodies what sets you apart. Our consultants help your teams frame it as a product, deliver it in increments and build it so that it remains changeable long after go-live. MLOps and LLMOps A model that works in a notebook is not a service in production. Our consultants help your teams establish the pipeline that makes it possible to deliver, monitor and correct your models, predictive and generative alike. Agile at scale Agile teams do not make an agile organisation. Our consultants help your teams sort out what happens between them: priorities, dependencies, integration and the way the work is funded. Data platform Warehouse, lake, lakehouse, data mesh: the right choice depends on your uses, your organisation and your constraints, not on the trend of the moment. Our consultants help your teams design a platform they know how to operate and whose cost remains clear. FinOps In the cloud, spending is decided by those who deploy, not by those who control it. Our consultants help make cost visible to the teams that incur it and establish the rules that allow it to be optimised without holding back delivery. IT architecture A useful architecture can be recognised by the decisions it makes simpler. Our consultants help your teams give the information system a target, a roadmap and integration rules that projects apply because they save them time. SRE and observability Reliability cannot be decreed and is not measured by the number of green lights. We help you define it from your users' point of view, measure it and make it a criterion for trade-offs between new features and stability.

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is the difference between DevOps and platform engineering?

DevOps is a way of working: the teams that develop an application take part in operating it, and delivery is automated. Platform engineering is an organisational response to the limits of this model at large scale. A dedicated team provides the others with a self-service platform, so that each one does not have to build its own pipeline.

What is an internal developer platform?

An internal developer platform is a set of self-service services and tools that a platform team makes available to development teams. It makes it possible to obtain an environment, deploy an application or create a database without going through a manual request, while complying with the organisation's security rules.

What is a golden path?

A golden path is a recommended, documented and maintained way of meeting a common need, for example releasing a web service to production. It is not mandatory. It is designed to be the most convenient route, so that teams choose it of their own accord and benefit from its security and operational settings.

Do you need a developer portal to do platform engineering?

No, and that is not where to start. A portal only has value if it gives access to capabilities that work. We recommend first delivering one or two complete golden paths, usable from the command line or through a code repository, then adding a portal when the catalogue justifies it.

Does platform engineering also concern data and AI teams?

Yes. Data processing and machine learning models also need reproducible environments, deployment pipelines and common rules. A well-designed platform offers them suitable golden paths, instead of leaving them to build a parallel toolset.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.