{"id":23412,"date":"2023-02-07T06:00:00","date_gmt":"2023-02-07T06:00:00","guid":{"rendered":"https:\/\/www.cycloid.io\/blogs\/7-platform-engineering-kpis-you-should-be-tracking\/"},"modified":"2026-03-02T06:03:27","modified_gmt":"2026-03-02T06:03:27","slug":"7-indicateurs-cles-de-performance-kpi-a-suivre-en-ingenierie-de-plateforme","status":"publish","type":"blogs","link":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/","title":{"rendered":"7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">L&rsquo;ing\u00e9nierie de plateforme est une approche de plus en plus populaire pour le d\u00e9veloppement logiciel, car elle offre des avantages tels qu&rsquo;un time-to-market plus rapide, une satisfaction accrue des d\u00e9veloppeurs et la suppression des silos d&rsquo;\u00e9quipe. Nous avons beaucoup \u00e9crit sur l&rsquo;ing\u00e9nierie de plateforme, notamment sur le fait qu&rsquo;elle n&rsquo;est pas nouvelle et que le DevOps est loin d&rsquo;\u00eatre mort. Cependant, \u00e9tant donn\u00e9 les difficult\u00e9s rencontr\u00e9es par de nombreuses entreprises pour concr\u00e9tiser la valeur ajout\u00e9e du DevOps, elles pourraient consid\u00e9rer la cr\u00e9ation de plateformes num\u00e9riques internes pour faciliter le d\u00e9veloppement logiciel comme un plan d&rsquo;action concret pour atteindre tous les objectifs du DevOps.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Mais comment \u00e9viter le pi\u00e8ge qui a emp\u00each\u00e9 80 % des entreprises d&rsquo;adopter le DevOps ?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Notre conseil : consid\u00e9rez votre plateforme comme un produit interne et vos \u00e9quipes comme vos clients. Cela signifie que vos indicateurs de performance doivent \u00eatre les m\u00eames que ceux utilis\u00e9s pour vos clients, adapt\u00e9s au contexte de l&rsquo;ing\u00e9nierie de plateforme.<\/span><\/p>\n<p><strong><span style=\"font-size: 24px;\">Objectifs cl\u00e9s de l&rsquo;ing\u00e9nierie de plateforme<\/span><\/strong><\/p>\n<p><span style=\"font-weight: 400;\">Lors de la d\u00e9finition de vos indicateurs de performance, il est essentiel de garder \u00e0 l&rsquo;esprit les objectifs de votre strat\u00e9gie d&rsquo;ing\u00e9nierie de plateforme. D&rsquo;apr\u00e8s le rapport \u00ab State of DevOps 2023 \u00bb, voici les principaux objectifs que les entreprises se sont fix\u00e9s pour leurs \u00e9quipes plateforme.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Former et responsabiliser les \u00e9quipes de d\u00e9veloppement et produit est une priorit\u00e9 majeure pour les \u00e9quipes plateforme, suivie de la vitesse d&rsquo;it\u00e9ration et des processus de s\u00e9curit\u00e9. Cette approche centr\u00e9e sur l&rsquo;humain est celle que vous devriez adopter pour vos indicateurs. R\u00e9inventer les outils ne repr\u00e9sente que la moiti\u00e9 du travail : vous devez vous assurer que vos collaborateurs ma\u00eetrisent les nouveaux frameworks. Rationaliser et automatiser les processus selon les bonnes pratiques DevX permet \u00e0 toute l&rsquo;organisation d&rsquo;\u00eatre plus agile et de gagner un avantage concurrentiel.<\/span><\/p>\n<p><span style=\"font-size: 24px; font-weight: bold;\">KPI de l&rsquo;ing\u00e9nierie de plateforme<\/span><\/p>\n<p><span style=\"font-weight: 400;\">D&rsquo;apr\u00e8s le rapport \u00ab State of DevOps 2023 \u00bb, apr\u00e8s l&rsquo;adoption de l&rsquo;ing\u00e9nierie de plateforme, la majorit\u00e9 des entreprises auraient constat\u00e9 des am\u00e9liorations en mati\u00e8re de fiabilit\u00e9 du syst\u00e8me (60 %), de productivit\u00e9 et d&rsquo;efficacit\u00e9 (59 %) et de normes de workflows (57 %), tandis que 42 % ont fait \u00e9tat d&rsquo;une r\u00e9duction du temps de d\u00e9veloppement.<\/span><\/p>\n<p><span style=\"font-size: 22px; font-weight: bold;\">Productivit\u00e9<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Mesurer le nombre de lignes de code produites par les d\u00e9veloppeurs en un temps donn\u00e9 est un indicateur obsol\u00e8te, d\u00e9sormais peut-\u00eatre utilis\u00e9 uniquement par des personnalit\u00e9s comme Elon Musk. La productivit\u00e9 des d\u00e9veloppeurs est un sujet d\u00e9licat. Si l&rsquo;ing\u00e9nierie de plateforme promet d&rsquo;acc\u00e9l\u00e9rer le d\u00e9veloppement logiciel, ce n&rsquo;est pas en augmentant la productivit\u00e9 des d\u00e9veloppeurs que cela se produit.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Il s&rsquo;agit plut\u00f4t de cr\u00e9er les conditions optimales pour que vos d\u00e9veloppeurs s&rsquo;\u00e9panouissent. R\u00e9fl\u00e9chissez aux goulots d&rsquo;\u00e9tranglement et aux obstacles auxquels vos \u00e9quipes sont confront\u00e9es quotidiennement, et \u00e0 leur d\u00e9pendance vis-\u00e0-vis des experts pour mener \u00e0 bien leurs t\u00e2ches. D\u00e9ploiements d&rsquo;infrastructures complexes, cr\u00e9ation de nouveaux environnements, livraison de fonctionnalit\u00e9s : tout cela requiert l&rsquo;aide des DevOps, ce qui ralentit in\u00e9vitablement les processus. Vos indicateurs cl\u00e9s de performance (KPI) doivent \u00eatre ax\u00e9s sur la rationalisation et la simplification du processus de livraison logicielle.<\/span><\/p>\n<ul>\n<li><strong>D\u00e9lai de livraison<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Il s&rsquo;agit d&rsquo;une mesure qui suit le temps \u00e9coul\u00e9 entre le lancement d&rsquo;une user story et sa disponibilit\u00e9 pour la livraison. Ce d\u00e9lai peut \u00e9galement inclure les discussions relatives \u00e0 la user story, sa dur\u00e9e d&rsquo;attente dans le backlog et le temps n\u00e9cessaire pour passer de sa prise en charge \u00e0 sa mise en production.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Si votre d\u00e9lai de livraison pour les modifications est trop long, cela indique clairement un blocage dans vos processus, emp\u00eachant ainsi la progression des \u00e9l\u00e9ments du backlog. Automatiser tout ce qui peut l&rsquo;\u00eatre contribue \u00e0 r\u00e9duire les d\u00e9lais de livraison, car cela d\u00e9montre la r\u00e9activit\u00e9 de vos \u00e9quipes face aux retours d&rsquo;information et leur capacit\u00e9 \u00e0 atteindre leurs objectifs.<\/span><\/p>\n<p><!--more--><\/p>\n<ul>\n<li><strong>\u00a0Fr\u00e9quence de d\u00e9ploiement<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">La fr\u00e9quence de d\u00e9ploiement mesure la fr\u00e9quence \u00e0 laquelle vos utilisateurs finaux d\u00e9ploient du code en production. C&rsquo;est un bon indicateur de la valeur ajout\u00e9e que vos \u00e9quipes d&rsquo;ing\u00e9nierie peuvent apporter aux clients. M\u00eame avec un flux de travail parfaitement rod\u00e9, la valeur ajout\u00e9e peut \u00eatre insuffisante si les d\u00e9ploiements ne sont pas assez fr\u00e9quents.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Une fr\u00e9quence de d\u00e9ploiement \u00e9lev\u00e9e montre que votre \u00e9quipe peut apporter des modifications fr\u00e9quentes au code et les mettre en production rapidement et sans d\u00e9lai. Plus le d\u00e9ploiement de la nouvelle infrastructure est simple pour vos utilisateurs finaux, plus il est rapide. Par cons\u00e9quent, cet indicateur retard\u00e9 montre que vos \u00e9quipes de d\u00e9veloppement adoptent efficacement les pratiques d&rsquo;int\u00e9gration et de livraison continues (CI\/CD), d\u00e9ploient fr\u00e9quemment de petits fragments de code et ma\u00eetrisent parfaitement l&rsquo;infrastructure.<\/span><\/p>\n<ul>\n<li><strong>Bonheur des d\u00e9veloppeurs<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Bien qu&rsquo;il puisse para\u00eetre paradoxal d&rsquo;associer le bien-\u00eatre des d\u00e9veloppeurs \u00e0 leur productivit\u00e9, il s&rsquo;av\u00e8re que ces deux \u00e9l\u00e9ments sont positivement corr\u00e9l\u00e9s. L&rsquo;ing\u00e9nierie de plateforme vise sp\u00e9cifiquement \u00e0 am\u00e9liorer l&rsquo;exp\u00e9rience des d\u00e9veloppeurs, c&rsquo;est pourquoi il est important de mesurer vos statistiques DevX.<\/span><\/p>\n<p><span style=\"font-size: 22px;\"><strong>Stabilit\u00e9<\/strong><\/span><\/p>\n<p><span style=\"font-weight: 400;\">La stabilit\u00e9 mesure votre capacit\u00e9 \u00e0 permettre aux ing\u00e9nieurs produit d&rsquo;apporter des modifications en toute confiance, sans impacter l&rsquo;exp\u00e9rience client.<\/span><\/p>\n<ul>\n<li><strong>Taux d&rsquo;\u00e9chec des modifications (CFR)<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Le taux d&rsquo;\u00e9chec des modifications mesure le pourcentage de d\u00e9ploiements en production ayant \u00e9chou\u00e9. Cet indicateur retard\u00e9 offre une vision claire de la qualit\u00e9 et de la stabilit\u00e9 du logiciel. Pour obtenir ce taux, divisez le nombre de d\u00e9ploiements ayant entra\u00een\u00e9 des \u00e9checs par le nombre total de d\u00e9ploiements.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">En surveillant cet indicateur dans le temps, vous pouvez \u00e9valuer l&rsquo;effort consacr\u00e9 \u00e0 la r\u00e9solution des probl\u00e8mes et celui consacr\u00e9 au d\u00e9ploiement de nouveau code. Au-del\u00e0 de 15 %, vos \u00e9quipes passent probablement trop de temps \u00e0 corriger les probl\u00e8mes. Cela signifie qu&rsquo;elles pourraient \u00eatre plus productives ailleurs, et que certains processus doivent \u00eatre am\u00e9lior\u00e9s.<\/span><\/p>\n<ul>\n<li><strong>Temps moyen de r\u00e9cup\u00e9ration (MTTR)<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Le temps moyen de r\u00e9cup\u00e9ration est un autre indicateur retard\u00e9 qui indique la rapidit\u00e9 avec laquelle un service peut reprendre son fonctionnement normal apr\u00e8s une interruption. Pour d\u00e9terminer cet indicateur de performance cl\u00e9 (KPI), calculez le temps n\u00e9cessaire au d\u00e9ploiement d&rsquo;un correctif apr\u00e8s le signalement d&rsquo;un probl\u00e8me.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">M\u00eame les meilleures \u00e9quipes DevOps subissent parfois des interruptions de service et des probl\u00e8mes impr\u00e9vus. Il est impossible d&#8217;emp\u00eacher les pannes, mais il est essentiel de conna\u00eetre le temps n\u00e9cessaire pour r\u00e9tablir le fonctionnement normal des syst\u00e8mes apr\u00e8s un incident.<\/span><\/p>\n<p><strong><span style=\"font-size: 20px;\"><span style=\"font-size: 22px;\">Efficacit\u00e9<\/span><\/span><\/strong><strong><span style=\"font-size: 20px;\">\u00a0<\/span><\/strong><\/p>\n<p><span style=\"font-weight: 400;\">La productivit\u00e9 et l&rsquo;efficacit\u00e9 sont souvent regroup\u00e9es, mais nous souhaitons nous concentrer sur les indicateurs d&rsquo;efficacit\u00e9 li\u00e9s au rapport co\u00fbt-efficacit\u00e9, notamment le co\u00fbt des ressources cloud, de l&rsquo;infrastructure et des licences, ainsi que celui des \u00e9quipes d&rsquo;ing\u00e9nierie de plateforme. L&rsquo;ing\u00e9nierie de plateforme vise l&rsquo;utilisation efficiente des ressources ; les modules <a href=\"https:\/\/www.cycloid.io\/fr\/solutions\/cycloid-pour-les-gestions-finops-et-greenops\/\">FinOps et GreenOps<\/a> optimiseront donc votre strat\u00e9gie de ressources.<\/span><\/p>\n<ul>\n<li><strong>Allocation des ressources<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">L&rsquo;allocation des ressources promeut les \u00e9changes constructifs sur l&rsquo;\u00e9quilibre \u00e0 trouver entre plusieurs objectifs et des ressources limit\u00e9es. L&rsquo;ing\u00e9nierie de plateforme devrait vous aider \u00e0 r\u00e9partir \u00e9quitablement les ressources limit\u00e9es et \u00e0 suivre pr\u00e9cis\u00e9ment leur utilisation. Cet indicateur sera particuli\u00e8rement appr\u00e9ci\u00e9 des dirigeants, car il permet de v\u00e9rifier si les ing\u00e9nieurs se concentrent sur les objectifs les plus importants de l&rsquo;entreprise.<\/span><\/p>\n<ul>\n<li><strong>Visibilit\u00e9 des co\u00fbts<\/strong><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Savoir o\u00f9 va votre argent vous permettra de d\u00e9tecter les d\u00e9passements de d\u00e9penses et le gaspillage li\u00e9s au cloud. Comme nous l&rsquo;avons d\u00e9j\u00e0 mentionn\u00e9, l&rsquo;efficacit\u00e9 des ressources est un pilier de l&rsquo;ing\u00e9nierie de plateforme. C&rsquo;est pourquoi nous encourageons les entreprises \u00e0 adopter une approche raisonn\u00e9e de leur consommation cloud.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Des indicateurs cl\u00e9s de performance (KPI) de co\u00fbts transparents vous aideront \u00e0 atteindre cet objectif. Permettre aux utilisateurs finaux et aux \u00e9quipes de plateforme de visualiser l&rsquo;impact financier de leurs architectures avant d\u00e9ploiement, ou d&rsquo;obtenir une vue d&rsquo;ensemble de toutes les d\u00e9penses cloud, sera un facteur d\u00e9terminant de votre r\u00e9ussite.<\/span><\/p>\n<p><strong><span style=\"font-size: 24px;\">Tableaux de bord KPI pour l&rsquo;ing\u00e9nierie de plateforme<\/span><\/strong><\/p>\n<p><span style=\"font-weight: 400;\">Nombre de ces KPI sont une responsabilit\u00e9 partag\u00e9e entre les \u00e9quipes ; gardez cela \u00e0 l&rsquo;esprit lors de la visualisation de vos indicateurs. La transparence et l&rsquo;observabilit\u00e9 contribuent \u00e0 d\u00e9cloisonner les \u00e9quipes ; il est donc important d&rsquo;envisager des tableaux de bord KPI complets et communs. Voici, par exemple, \u00e0 quoi ressemblent les KPI chez Cycloid :<\/span><\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" style=\"height: auto; max-width: 100%; width: 590px;\" src=\"https:\/\/6369062.fs1.hubspotusercontent-na1.net\/hubfs\/6369062\/1000%20%E2%80%94%20Dashboard@3x.png\" alt=\"1000 \u2014 Dashboard@3x\" width=\"590\" height=\"445\" \/><\/p>\n<p><span style=\"font-weight: bold; font-size: 24px;\">Conclusion<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00c9tant donn\u00e9 qu&rsquo;un tiers des \u00e9quipes de plateforme rencontrent encore des difficult\u00e9s d&rsquo;adoption de leur plateforme, le suivi de votre progression en mati\u00e8re d&rsquo;adoption devrait figurer parmi vos KPI principaux. Apr\u00e8s tout, une plateforme est con\u00e7ue pour \u00eatre b\u00e9n\u00e9fique \u00e0 l&rsquo;ensemble de l&rsquo;entreprise et pour renforcer la collaboration entre les \u00e9quipes ; cela exige donc la coop\u00e9ration de tous.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Quels que soient les indicateurs choisis, il est important de d\u00e9finir des attentes r\u00e9alistes au sein de l&rsquo;entreprise durant les premi\u00e8res ann\u00e9es d&rsquo;adoption de la plateforme par l&rsquo;\u00e9quipe produit. Vos KPI \u00e9volueront au fil de votre parcours d&rsquo;ing\u00e9nierie de plateforme, mais dans un premier temps, concentrez-vous sur la simplification de l&rsquo;int\u00e9gration et de l&rsquo;exploitation des donn\u00e9es par les \u00e9quipes plateforme et produit.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: center;\"><span style=\"font-size: 16px;\"><em><span style=\"font-weight: 400;\">Int\u00e9ress\u00e9(e) par l&rsquo;ing\u00e9nierie de plateforme version Cycloid ? Demandez une d\u00e9monstration personnalis\u00e9e \u00e0 notre \u00e9quipe :<\/span><\/em><\/span><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Contactez notre \u00e9quipe<\/strong><\/p>\n<p><script charset=\"utf-8\" src=\"\/hs\/cta\/cta\/current.js\"><\/script><script type=\"text\/javascript\"> hbspt.cta._relativeUrls=true;hbspt.cta.load(6369062, '2fa281d7-afe7-428b-94b2-6e02f8188729', {\"useNewLoader\":\"true\",\"region\":\"na1\"}); <\/script><\/p>\n","protected":false},"featured_media":7734,"parent":0,"template":"","meta":{"_acf_changed":false},"language":[],"tags":[33,26,31],"class_list":["post-23412","blogs","type-blogs","status-publish","has-post-thumbnail","hentry","tags-devx","tags-platform-engineering","tags-technical"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme\" \/>\n<meta property=\"og:description\" content=\"Platform engineering is becoming an increasingly popular approach to software delivery because it offers benefits such as improved time-to-market speed, increased developer happiness, and breaking down of team silos. We wrote extensively about platform engineering, specifically that it\u2019s not, in fact, new and DevOps is not dead. However, given how many enterprises have struggled with delivering DevOps business value, they might view building internal digital platforms to aid software delivery as an actionable plan to achieve everything DevOps ever promised.But how do you avoid falling into the same trap that held 80% of companies back from adopting DevOps?Our advice: treat your platform like an internal product, and your wider teams as your customers. This means that your success metrics should be the same as you would use for your customers - with a platform engineering twist.&nbsp;Key goals of Platform EngineeringWhen setting up your success metrics, it\u2019s important to not lose sight of what your Platform Engineering strategy should aim for. According to the 2023 State of DevOps report, these were the top goals companies set for their platform teams.Educating and empowering developer and product teams is a major priority for platform teams, followed by iteration speed and security processes. This people-centric approach is the same one you should adopt in your metrics. Reinventing tools is only half the job - you need to make sure your people are comfortable using the new frameworks. Streamlining and automating processes according to DevX best practices helps the entire organization move more quickly and drive a competitive edge.Platform Engineering KPIsAccording to the 2023 State of DevOps report, after adopting Platform Engineering, the majority of enterprises saw improvements in system reliability (60%), productivity and efficiency (59%), and workflow standards (57%), while 42% reported improved development time.ProductivityMeasuring lines of code produced by developers in X amount of time is an outdated metric used these days perhaps only by the likes of Elon Musk. Developer productivity is a sensitive subject, and while platform engineering promises to speed up software development, it doesn\u2019t happen by making developers deliver more.Instead, it\u2019s about creating the best conditions for your devs to thrive in. Think about the bottlenecks and obstacles that your teams have to deal with daily and how much they have to rely on experts to get their work done. Complex infrastructure deployments, creating new environments, shipping features - all these require DevOps help, which inevitably clogs up processes. KPIs centered around streamlining and simplifying the software delivery process should be your focus. Lead Time This is a measurement that tracks the time from when a user story is initiated to when it\u2019s ready for delivery. This time can also include discussions about the user story, how long it was waiting in the backlog, and how much time it took the story to move from pickup to release.&nbsp;If your lead time for changes is too high, it\u2019s a clear sign of a roadblock somewhere in your processes, causing items in the backlog not to move along. Automating whatever could be automated will help keep your lead time low, as it shows your teams are quick to adapt to feedback and deliver on their goals.  &nbsp;Deployment Frequency Deployment frequency tracks how often your end-users deploy code to production. It\u2019s a good measure of the value your engineering teams can deliver to customers. However well-oiled your workflow may be, it can fail to deliver sufficient value if you\u2019re not deploying frequently enough.High deployment frequency shows that your team can make frequent changes to code and make it live \u2014 with little fuss and delays. The easier time your end-users have deploying new infra, the faster it&#039;s going to happen. Consequently, this lagging indicator shows that your development teams are efficiently adopting continuous integration and continuous delivery (CI\/CD) practices, deploying small pieces of code frequently, and having a solid grasp of the infrastructure Developer Happiness While it might seem a bit unethical to group developer happiness with productivity, fortunately, it turns out that developer happiness and productivity are positively correlated. Platform engineering is specifically aimed at improving the developer experience, which is why measuring your DevX stats is important.StabilityStability measures your ability to enable product engineers to make changes confidently and without breaking the end customer experience.&nbsp; Change Failure Rate (CFR) Change failure rate measures the percentage of failed deployments to production. This lagging indicator can give you a clear view of software quality and stability. Divide the number of deployments that caused failures by the total number of deployments to get this metric.By monitoring this metric over time, you can get a good idea of how much effort goes into addressing problems and how much goes into releasing new code. When it\u2019s above 15%, your teams are probably spending too much time fixing problems. This means they could be more productive elsewhere, or some processes need to be improved. Mean Time to Recover (MTTR) Mean time to recover is another lagging indicator that shows you how quickly a service can resume normal operation after an interruption. To determine this KPI, calculate how long it takes to deploy a patch after an issue is reported.&nbsp;Even the best DevOps teams experience unanticipated downtime and issues from time to time. You can\u2019t stop failures from happening \u2014 but you need to know how long it takes to get things back up and running after they do.Efficiency&nbsp;Productivity and efficiency often get grouped in the same category, but we want to specifically look at cost-effective efficiency metrics, which include the cost of cloud resources, infrastructure, and licenses, as well as the cost of platform engineering teams. Platform engineering is all about the efficient use of resources, so FinOps and GreenOps modules would benefit your resource strategy. Resource allocation Resource allocation offers the foundation for productive conversations about balancing several objectives with a fixed amount of resources. Platform engineering should help you distribute limited resources evenly and know exactly where they are spent. Executives will appreciate this metric since it demonstrates whether engineers are focusing on the company\u2019s most crucial goals.&nbsp; Cost observability Knowing where you spend your money will help you catch overrunning cloud expenses and waste. As we\u2019ve already mentioned, resource efficiency is one of the pillars of platform engineering, and that\u2019s why we encourage companies to take a sober approach to their cloud consumption.&nbsp;Transparent cost KPIs will help you achieve this goal. Giving end-users and platform teams alike the ability to see the cost impact of their architecture designs before deploying or a holistic overview of all cloud expenses will be the make-or-break element in your success.&nbsp;Platform Engineering KPI dashboards&nbsp;Many of these KPIs have a shared responsibility between teams - keep this in mind when visualizing your metrics. Transparency and observability are one of the things that contribute to breaking down team silos, so shared comprehensive KPI dashboards are something to consider. Consider, for example, what KPIs look like at Cycloid: Bottom lineGiven that a third of platform teams are still struggling with the wider team\u2019s resistance to platform adoption, keeping an eye on your adoption progress should be among your wider KPIs. After all, a platform is meant to benefit the whole company and bring teams to work closer together, and that requires cooperation on all sides.&nbsp;No matter which metrics you choose, it\u2019s important to set realistic expectations within the company during the early years of platform team adoption. Your KPIs will evolve as you move through your Platform Engineering journey, but in the early stages, you should focus on making it much easier for platform and product teams to ingest their data and make it actionable. Curious about Cycloid Platform Engineering? Get a personalized demo from our team:{{cta(&#039;2fa281d7-afe7-428b-94b2-6e02f8188729&#039;)}}\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T06:03:27+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cycloid.io\/wp-content\/uploads\/2023\/02\/Blog_post_PE-v1-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1509\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blog\\\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\\\/\",\"url\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blog\\\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\\\/\",\"name\":\"7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blog\\\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blog\\\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cycloid.io\\\/wp-content\\\/uploads\\\/2023\\\/02\\\/Blog_post_PE-v1-1.png\",\"datePublished\":\"2023-02-07T06:00:00+00:00\",\"dateModified\":\"2026-03-02T06:03:27+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blog\\\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\\\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blog\\\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blog\\\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.cycloid.io\\\/wp-content\\\/uploads\\\/2023\\\/02\\\/Blog_post_PE-v1-1.png\",\"contentUrl\":\"https:\\\/\\\/www.cycloid.io\\\/wp-content\\\/uploads\\\/2023\\\/02\\\/Blog_post_PE-v1-1.png\",\"width\":2400,\"height\":1509},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blog\\\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Blogs\",\"item\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/blogs\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/\",\"name\":\"\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cycloid.io\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/","og_locale":"fr_FR","og_type":"article","og_title":"7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme","og_description":"Platform engineering is becoming an increasingly popular approach to software delivery because it offers benefits such as improved time-to-market speed, increased developer happiness, and breaking down of team silos. We wrote extensively about platform engineering, specifically that it\u2019s not, in fact, new and DevOps is not dead. However, given how many enterprises have struggled with delivering DevOps business value, they might view building internal digital platforms to aid software delivery as an actionable plan to achieve everything DevOps ever promised.But how do you avoid falling into the same trap that held 80% of companies back from adopting DevOps?Our advice: treat your platform like an internal product, and your wider teams as your customers. This means that your success metrics should be the same as you would use for your customers - with a platform engineering twist.&nbsp;Key goals of Platform EngineeringWhen setting up your success metrics, it\u2019s important to not lose sight of what your Platform Engineering strategy should aim for. According to the 2023 State of DevOps report, these were the top goals companies set for their platform teams.Educating and empowering developer and product teams is a major priority for platform teams, followed by iteration speed and security processes. This people-centric approach is the same one you should adopt in your metrics. Reinventing tools is only half the job - you need to make sure your people are comfortable using the new frameworks. Streamlining and automating processes according to DevX best practices helps the entire organization move more quickly and drive a competitive edge.Platform Engineering KPIsAccording to the 2023 State of DevOps report, after adopting Platform Engineering, the majority of enterprises saw improvements in system reliability (60%), productivity and efficiency (59%), and workflow standards (57%), while 42% reported improved development time.ProductivityMeasuring lines of code produced by developers in X amount of time is an outdated metric used these days perhaps only by the likes of Elon Musk. Developer productivity is a sensitive subject, and while platform engineering promises to speed up software development, it doesn\u2019t happen by making developers deliver more.Instead, it\u2019s about creating the best conditions for your devs to thrive in. Think about the bottlenecks and obstacles that your teams have to deal with daily and how much they have to rely on experts to get their work done. Complex infrastructure deployments, creating new environments, shipping features - all these require DevOps help, which inevitably clogs up processes. KPIs centered around streamlining and simplifying the software delivery process should be your focus. Lead Time This is a measurement that tracks the time from when a user story is initiated to when it\u2019s ready for delivery. This time can also include discussions about the user story, how long it was waiting in the backlog, and how much time it took the story to move from pickup to release.&nbsp;If your lead time for changes is too high, it\u2019s a clear sign of a roadblock somewhere in your processes, causing items in the backlog not to move along. Automating whatever could be automated will help keep your lead time low, as it shows your teams are quick to adapt to feedback and deliver on their goals.  &nbsp;Deployment Frequency Deployment frequency tracks how often your end-users deploy code to production. It\u2019s a good measure of the value your engineering teams can deliver to customers. However well-oiled your workflow may be, it can fail to deliver sufficient value if you\u2019re not deploying frequently enough.High deployment frequency shows that your team can make frequent changes to code and make it live \u2014 with little fuss and delays. The easier time your end-users have deploying new infra, the faster it's going to happen. Consequently, this lagging indicator shows that your development teams are efficiently adopting continuous integration and continuous delivery (CI\/CD) practices, deploying small pieces of code frequently, and having a solid grasp of the infrastructure Developer Happiness While it might seem a bit unethical to group developer happiness with productivity, fortunately, it turns out that developer happiness and productivity are positively correlated. Platform engineering is specifically aimed at improving the developer experience, which is why measuring your DevX stats is important.StabilityStability measures your ability to enable product engineers to make changes confidently and without breaking the end customer experience.&nbsp; Change Failure Rate (CFR) Change failure rate measures the percentage of failed deployments to production. This lagging indicator can give you a clear view of software quality and stability. Divide the number of deployments that caused failures by the total number of deployments to get this metric.By monitoring this metric over time, you can get a good idea of how much effort goes into addressing problems and how much goes into releasing new code. When it\u2019s above 15%, your teams are probably spending too much time fixing problems. This means they could be more productive elsewhere, or some processes need to be improved. Mean Time to Recover (MTTR) Mean time to recover is another lagging indicator that shows you how quickly a service can resume normal operation after an interruption. To determine this KPI, calculate how long it takes to deploy a patch after an issue is reported.&nbsp;Even the best DevOps teams experience unanticipated downtime and issues from time to time. You can\u2019t stop failures from happening \u2014 but you need to know how long it takes to get things back up and running after they do.Efficiency&nbsp;Productivity and efficiency often get grouped in the same category, but we want to specifically look at cost-effective efficiency metrics, which include the cost of cloud resources, infrastructure, and licenses, as well as the cost of platform engineering teams. Platform engineering is all about the efficient use of resources, so FinOps and GreenOps modules would benefit your resource strategy. Resource allocation Resource allocation offers the foundation for productive conversations about balancing several objectives with a fixed amount of resources. Platform engineering should help you distribute limited resources evenly and know exactly where they are spent. Executives will appreciate this metric since it demonstrates whether engineers are focusing on the company\u2019s most crucial goals.&nbsp; Cost observability Knowing where you spend your money will help you catch overrunning cloud expenses and waste. As we\u2019ve already mentioned, resource efficiency is one of the pillars of platform engineering, and that\u2019s why we encourage companies to take a sober approach to their cloud consumption.&nbsp;Transparent cost KPIs will help you achieve this goal. Giving end-users and platform teams alike the ability to see the cost impact of their architecture designs before deploying or a holistic overview of all cloud expenses will be the make-or-break element in your success.&nbsp;Platform Engineering KPI dashboards&nbsp;Many of these KPIs have a shared responsibility between teams - keep this in mind when visualizing your metrics. Transparency and observability are one of the things that contribute to breaking down team silos, so shared comprehensive KPI dashboards are something to consider. Consider, for example, what KPIs look like at Cycloid: Bottom lineGiven that a third of platform teams are still struggling with the wider team\u2019s resistance to platform adoption, keeping an eye on your adoption progress should be among your wider KPIs. After all, a platform is meant to benefit the whole company and bring teams to work closer together, and that requires cooperation on all sides.&nbsp;No matter which metrics you choose, it\u2019s important to set realistic expectations within the company during the early years of platform team adoption. Your KPIs will evolve as you move through your Platform Engineering journey, but in the early stages, you should focus on making it much easier for platform and product teams to ingest their data and make it actionable. Curious about Cycloid Platform Engineering? Get a personalized demo from our team:{{cta('2fa281d7-afe7-428b-94b2-6e02f8188729')}}","og_url":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/","article_modified_time":"2026-03-02T06:03:27+00:00","og_image":[{"width":2400,"height":1509,"url":"https:\/\/www.cycloid.io\/wp-content\/uploads\/2023\/02\/Blog_post_PE-v1-1.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/","url":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/","name":"7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme","isPartOf":{"@id":"https:\/\/www.cycloid.io\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/#primaryimage"},"image":{"@id":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cycloid.io\/wp-content\/uploads\/2023\/02\/Blog_post_PE-v1-1.png","datePublished":"2023-02-07T06:00:00+00:00","dateModified":"2026-03-02T06:03:27+00:00","breadcrumb":{"@id":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/#primaryimage","url":"https:\/\/www.cycloid.io\/wp-content\/uploads\/2023\/02\/Blog_post_PE-v1-1.png","contentUrl":"https:\/\/www.cycloid.io\/wp-content\/uploads\/2023\/02\/Blog_post_PE-v1-1.png","width":2400,"height":1509},{"@type":"BreadcrumbList","@id":"https:\/\/www.cycloid.io\/fr\/blog\/7-indicateurs-cles-de-performance-a-suivre-en-ingenierie-de-plateforme\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cycloid.io\/fr\/"},{"@type":"ListItem","position":2,"name":"Blogs","item":"https:\/\/www.cycloid.io\/fr\/blogs\/"},{"@type":"ListItem","position":3,"name":"7 indicateurs cl\u00e9s de performance (KPI) \u00e0 suivre en ing\u00e9nierie de plateforme"}]},{"@type":"WebSite","@id":"https:\/\/www.cycloid.io\/fr\/#website","url":"https:\/\/www.cycloid.io\/fr\/","name":"","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cycloid.io\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"}]}},"_links":{"self":[{"href":"https:\/\/www.cycloid.io\/fr\/wp-json\/wp\/v2\/blogs\/23412","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cycloid.io\/fr\/wp-json\/wp\/v2\/blogs"}],"about":[{"href":"https:\/\/www.cycloid.io\/fr\/wp-json\/wp\/v2\/types\/blogs"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cycloid.io\/fr\/wp-json\/wp\/v2\/media\/7734"}],"wp:attachment":[{"href":"https:\/\/www.cycloid.io\/fr\/wp-json\/wp\/v2\/media?parent=23412"}],"wp:term":[{"taxonomy":"language","embeddable":true,"href":"https:\/\/www.cycloid.io\/fr\/wp-json\/wp\/v2\/language?post=23412"},{"taxonomy":"tags","embeddable":true,"href":"https:\/\/www.cycloid.io\/fr\/wp-json\/wp\/v2\/tags?post=23412"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}