[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"portal-settings:stajic:fr":3,"public-menus:all":38,"post:metrics:fr":205,"related:post:metrics:fr:1":816},{"statusCode":4,"data":5,"message":37},200,{"tenantId":6,"lang":7,"defaultLang":8,"siteUrl":9,"contactEmail":10,"brandName":11,"logoUrl":12,"siteName":11,"siteDescription":13,"ogImage":10,"robotsIndex":14,"socialLinks":10,"reservedSlugs":10,"seoPolicy":15},"stajic","fr","de","https:\u002F\u002Fstajic.de",null,"Stajic Platform","\u002FLogo_Planet.svg","Stajic Portal",true,{"branding":16,"relatedContent":17,"crossDomainLinks":18},{"logoUrl":12},{"enabled":14},[19,22,25,28,31,34],{"url":20,"label":21,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Ffigure.rocks","figure.rocks",{"url":23,"label":24,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Floving.rocks","loving.rocks",{"url":26,"label":27,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.com","bazify.com",{"url":29,"label":30,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.de","bazify.de",{"url":32,"label":33,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.at","bazify.at",{"url":35,"label":36,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.ba","bazify.ba","Portal settings resolved",[39,45],{"id":40,"name":41,"location":42,"isActive":14,"isDefault":43,"items":44},1,"main-navigation","header",false,[],{"id":46,"name":47,"location":48,"isActive":14,"isDefault":14,"items":49},4,"main-menu","sidebar",[50,66,79,93,103,118,133],{"id":51,"title":52,"url":60,"target":61,"icon":62,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":64,"portfolioId":10,"children":65},"item-18",{"de":53,"en":54,"es":55,"fr":56,"it":54,"ru":57,"sr":58,"zh":59},"Startseite","Home","Inicio","Accueil","Главная","Почетна","首页","\u002Ffull-stack-web-developer-munich-performance-seo-and-maintainable-builds","_self","i-lucide-home","page",111,[],{"id":67,"title":68,"url":75,"target":61,"icon":76,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":77,"portfolioId":10,"children":78},"item-22",{"de":69,"en":69,"es":70,"fr":69,"it":71,"ru":72,"sr":73,"zh":74},"Vision","Visión","Visione","Видение","Визија","想象","\u002Fueber-uns-webdesign-muenchen-webaplikation","i-lucide-eye",113,[],{"id":80,"title":81,"url":89,"target":61,"icon":90,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":91,"portfolioId":10,"children":92},"item-19",{"de":82,"en":83,"es":84,"fr":83,"it":85,"ru":86,"sr":87,"zh":88},"Leistungen","Services","Servicios","Servizi","Услуги","Услуге","服务","\u002Fservices-dienstleistungen-muenchen","i-lucide-wrench",116,[],{"id":94,"title":95,"url":99,"target":61,"icon":100,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":101,"portfolioId":10,"children":102},"item-23",{"de":96,"en":96,"es":96,"fr":96,"it":96,"ru":97,"sr":97,"zh":98},"Blog","Блог","博客","\u002Fblog","i-lucide-book-open",112,[],{"id":104,"title":105,"url":114,"target":61,"icon":115,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":116,"portfolioId":10,"children":117},"item-32",{"de":106,"en":107,"es":108,"fr":109,"it":110,"ru":111,"sr":112,"zh":113},"Neue Technologien","New Technologies","Nuevas tecnologías","Nouvelles technologies","Nuove tecnologie","Новые технологии","Нове технологије","新技术！","\u002Fneue-webtechnologien","i-lucide-sparkles",122,[],{"id":119,"title":120,"url":129,"target":61,"icon":130,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":131,"portfolioId":10,"children":132},"item-20",{"de":121,"en":122,"es":123,"fr":124,"it":125,"ru":126,"sr":127,"zh":128},"Kontakt","Contact us!","Contacto","Contact","Contatto","Контакт","Контактирајте нас","联系我们！","\u002Fcontact","i-lucide-mail",115,[],{"id":134,"title":135,"url":144,"target":61,"icon":145,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":146,"portfolioId":10,"children":147},"item-21",{"de":136,"en":137,"es":138,"fr":139,"it":140,"ru":141,"sr":142,"zh":143},"Unsere Arbeit","Our Work","Nuestro trabajo","Nos réalisations","I nostri lavori","Наши работы","Наши радови","文件夹","\u002Fportfolio","i-lucide-briefcase",114,[148,161,175,181,193],{"id":149,"title":150,"url":144,"target":61,"icon":159,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":146,"portfolioId":10,"children":160},"item-24",{"de":151,"en":152,"es":153,"fr":154,"it":155,"ru":156,"sr":157,"zh":158},"Alle Projekte","All Projects","Todos los proyectos","Tous les projets","Tutti i progetti","Все проекты","Сви пројекти","所有项目","i-lucide-grid-3x3",[],{"id":162,"title":163,"url":171,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":174},"item-29",{"de":164,"en":165,"es":166,"fr":167,"it":168,"ru":169,"sr":170,"zh":143},"Local Roots, Global Reach","Local Roots - Global Reach","Empresa local ","Entreprise locale","Azienda locale","Местная компания","Локално предузеће глобално тржиште","\u002Fportfolio\u002Flocal-roots-global-reach-communication-media-systems-for-modern-business","i-lucide-folder","custom",[],{"id":176,"title":177,"url":179,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":180},"item-28",{"de":178,"en":178,"es":178,"fr":178,"it":178,"ru":178,"sr":178,"zh":178},"Solr Suggester","\u002Fportfolio\u002Fsolr-fuzzy-suggester-und-solr-infix-suggester-abfrage-ueber-ajax-und-filterung",[],{"id":182,"title":183,"url":191,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":192},"item-27",{"de":184,"en":185,"es":186,"fr":187,"it":188,"ru":189,"sr":190,"zh":185},"Firmenwebseite SEO","Company Website SEO","Sitio web corporativo SEO","Site web d’entreprise SEO","Sito web aziendale SEO","Корпоративный сайт SEO","Пословна веб-страница SEO","\u002Fportfolio\u002Fseo-sem-branding-mobile-webseite-muenchen",[],{"id":194,"title":195,"url":203,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":204},"item-31",{"de":196,"en":197,"es":198,"fr":199,"it":200,"ru":201,"sr":202,"zh":197},"Digitalisierungsportal","Digitalization Portal","Portal de digitalización","Portail de numérisation","Portale di digitalizzazione","Портал цифровизации","Портал за дигитализацију","\u002Fportfolio\u002Fdigitalisierungsportal-archiv-museum-bibliothek-ead-lido-mets-mods",[],{"statusCode":4,"data":206,"message":815},{"id":207,"title":208,"slug":209,"content":210,"contentJson":211,"excerpt":282,"featuredImage":283,"featuredImageAlt":284,"featuredImageCaption":10,"featuredImageTitle":10,"featuredImageCopyright":10,"featuredImageAuthor":10,"featuredImageSourceUrl":10,"featuredImageLicense":10,"featuredImageIsAiGenerated":43,"status":285,"publishedAt":286,"createdAt":287,"updatedAt":288,"seoLocalePaths":289,"categories":298,"author":302,"translations":307},"437","Guide complet des métriques pour la livraison et la gestion du changement","metrics","\u003Cp># Guide complet des métriques pour la livraison et la gestion du changement\u003C\u002Fp>\n\u003Cp>Dans les environnements d'entreprise, une livraison et une gestion du changement efficaces reposent sur des analyses basées sur les données. Les métriques constituent le fondement de l'évaluation des performances, de l'identification des goulots d'étranglement et de l'alignement avec les objectifs stratégiques. Ce guide couvre les métriques essentielles des pipelines de livraison, des processus de changement et de la réalisation globale de la valeur, avec des étapes pratiques pour la mise en œuvre.\u003C\u002Fp>\n\u003Cp>## Pourquoi les métriques sont importantes dans la livraison et le changement\u003C\u002Fp>\n\u003Cp>Les métriques transforment les opinions subjectives en données objectives, permettant aux équipes de :\n- Suivre les progrès par rapport aux objectifs\n- Prédire et atténuer les risques\n- Optimiser l'allocation des ressources\n- Démontrer le ROI aux parties prenantes\u003C\u002Fp>\n\u003Cp>Sans métriques robustes, les organisations risquent des efforts cloisonnés, des temps d'arrêt prolongés et des transformations échouées.\u003C\u002Fp>\n\u003Cp>## Métriques principales de livraison\u003C\u002Fp>\n\u003Cp>### 1. Fréquence de déploiement\nMesure la fréquence à laquelle le code est déployé en production.\n- **Objectif** : Quotidien ou plusieurs fois par jour pour les meilleurs performeurs (normes DORA)\n- **Calcul** : Nombre de déploiements par jour\u002Fsemaine\u002Fmois\n- **Étapes pratiques** : 1. Intégrer le suivi des déploiements dans votre pipeline CI\u002FCD 2. Segmenter par environnement (dev\u002Fstaging\u002Fprod) 3. Comparer aux normes de l'industrie\u003C\u002Fp>\n\u003Cp>### 2. Délai de mise en œuvre des changements\nTemps entre le commit et le déploiement en production.\n- **Objectif** : Moins d'un jour\n- **Calcul** : Temps moyen pour tous les changements\n- **Étapes pratiques** : 1. Utiliser des outils comme GitHub Actions ou Jenkins pour la journalisation automatisée 2. Identifier les retards dans les étapes de revue, de test ou d'approbation 3. Automatiser autant que possible pour réduire les goulots d'étranglement humains\u003C\u002Fp>\n\u003Cp>### 3. Taux d'échec des changements\nPourcentage de déploiements causant des défaillances en production.\n- **Objectif** : 0-15%\n- **Calcul** : (Changements échoués \u002F Total des changements) × 100\n- **Étapes pratiques** : 1. Définir « échec » (ex. : rollback, hotfix, service dégradé >1h) 2. Implémenter des déploiements canary et des feature flags 3. Réaliser des post-mortems sur les échecs\u003C\u002Fp>\n\u003Cp>### 4. Temps moyen de récupération (MTTR)\nTemps moyen pour restaurer le service après une défaillance.\n- **Objectif** : Moins d'une heure\n- **Calcul** : Temps d'arrêt total \u002F Nombre d'incidents\n- **Étapes pratiques** : 1. Configurer des alertes avec PagerDuty ou Opsgenie 2. Automatiser les procédures de rollback 3. Exécuter des exercices d'ingénierie du chaos\u003C\u002Fp>\n\u003Cp>## Métriques clés de gestion du changement\u003C\u002Fp>\n\u003Cp>### 1. Taux de succès des changements\nProportion des changements mis en œuvre sans problèmes.\n- **Objectif** : >85%\n- **Calcul** : (Changements réussis \u002F Total des changements) × 100\n- **Étapes pratiques** : 1. Standardiser les modèles de demande de changement 2. Exiger des évaluations des risques et des revues par les pairs 3. Suivre via des outils ITSM comme ServiceNow\u003C\u002Fp>\n\u003Cp>### 2. Volume de changements et arriéré\nNombre de changements traités vs. en attente.\n- **Objectif** : Arriéré \u003C10% du volume mensuel\n- **Calcul** : Changements en attente \u002F Total soumis\n- **Étapes pratiques** : 1. Prioriser en utilisant la méthode MoSCoW 2. Mettre en place des comités consultatifs sur les changements (CAB) 3. Surveiller le temps de cycle de la demande à l'approbation\u003C\u002Fp>\n\u003Cp>### 3. Pourcentage de changements d'urgence\nRatio des changements urgents par rapport au total des changements.\n- **Objectif** : \u003C10%\n- **Calcul** : (Changements d'urgence \u002F Total) × 100\n- **Étapes pratiques** : 1. Analyser les causes profondes des urgences 2. Passer à une maintenance proactive 3. Appliquer des revues post-changement\u003C\u002Fp>\n\u003Cp>## Métriques de réalisation de la valeur\u003C\u002Fp>\n\u003Cp>### 1. Valeur métier livrée\nQuantifie l'impact des changements sur les résultats clés.\n- **Exemples** : Augmentation des revenus, économies de coûts, engagement des utilisateurs\n- **Calcul** : Delta des KPI avant\u002Faprès le changement\n- **Étapes pratiques** : 1. Étiqueter les changements avec les résultats métier attendus 2. Utiliser des frameworks OKR pour l'alignement 3. Produire des tableaux de bord trimestriels de la valeur\u003C\u002Fp>\n\u003Cp>### 2. Satisfaction client (CSAT)\nRetours sur les changements livrés.\n- **Objectif** : >4\u002F5\n- **Calcul** : Note moyenne des enquêtes post-déploiement\n- **Étapes pratiques** : 1. Automatiser les enquêtes NPS\u002FCSAT 2. Corréler avec les métriques de déploiement 3. Itérer en fonction des retours qualitatifs\u003C\u002Fp>\n\u003Cp>## Mise en œuvre d'un cadre de métriques\u003C\u002Fp>\n\u003Cp>1. **Sélectionner les métriques** : Commencez par les quatre métriques clés de DORA, puis ajoutez des métriques spécifiques aux changements.\n2. **Outils** : Utilisez des plateformes d'observabilité (Datadog, New Relic) intégrées à l'ITSM.\n3. **Tableaux de bord** : Créez des vues en temps réel dans Grafana ou Tableau.\n4. **Analyse comparative** : Comparez avec les pairs du secteur via le rapport Accelerate State of DevOps.\n5. **Rythme de revue** : Revues hebdomadaires par l'équipe, mises à jour mensuelles pour la direction.\n6. **Boucles d'action** : Reliez les métriques aux rétrospectives et à la planification PI.\u003C\u002Fp>\n\u003Cp>## Pièges courants et bonnes pratiques\u003C\u002Fp>\n\u003Cp>- **Piège** : Métriques de vanité (par ex. lignes de code) – Concentrez-vous sur les résultats.\n- **Bonne pratique** : Le contexte compte ; segmentez par équipe\u002Fservice.\n- **Piège** : Surcharge de métriques – Limitez-vous à 7-10 métriques principales.\n- **Bonne pratique** : Automatisez la collecte pour garantir l'exactitude.\u003C\u002Fp>\n\u003Cp>Affinez régulièrement vos métriques pour refléter l'évolution des priorités. Pour réussir à l'échelle de l'entreprise, intégrez-les à vos modèles de référence pour la livraison et le changement.\u003C\u002Fp>",{"time":212,"blocks":213,"version":281},1781624251976,[214,218,221,224,227,230,233,236,239,242,245,248,251,254,257,260,263,266,269,272,275,278],{"data":215,"type":217},{"text":216},"# Guide complet des métriques pour la livraison et la gestion du changement","paragraph",{"data":219,"type":217},{"text":220},"Dans les environnements d'entreprise, une livraison et une gestion du changement efficaces reposent sur des analyses basées sur les données. Les métriques constituent le fondement de l'évaluation des performances, de l'identification des goulots d'étranglement et de l'alignement avec les objectifs stratégiques. Ce guide couvre les métriques essentielles des pipelines de livraison, des processus de changement et de la réalisation globale de la valeur, avec des étapes pratiques pour la mise en œuvre.",{"data":222,"type":217},{"text":223},"## Pourquoi les métriques sont importantes dans la livraison et le changement",{"data":225,"type":217},{"text":226},"Les métriques transforment les opinions subjectives en données objectives, permettant aux équipes de :\n- Suivre les progrès par rapport aux objectifs\n- Prédire et atténuer les risques\n- Optimiser l'allocation des ressources\n- Démontrer le ROI aux parties prenantes",{"data":228,"type":217},{"text":229},"Sans métriques robustes, les organisations risquent des efforts cloisonnés, des temps d'arrêt prolongés et des transformations échouées.",{"data":231,"type":217},{"text":232},"## Métriques principales de livraison",{"data":234,"type":217},{"text":235},"### 1. Fréquence de déploiement\nMesure la fréquence à laquelle le code est déployé en production.\n- **Objectif** : Quotidien ou plusieurs fois par jour pour les meilleurs performeurs (normes DORA)\n- **Calcul** : Nombre de déploiements par jour\u002Fsemaine\u002Fmois\n- **Étapes pratiques** : 1. Intégrer le suivi des déploiements dans votre pipeline CI\u002FCD 2. Segmenter par environnement (dev\u002Fstaging\u002Fprod) 3. Comparer aux normes de l'industrie",{"data":237,"type":217},{"text":238},"### 2. Délai de mise en œuvre des changements\nTemps entre le commit et le déploiement en production.\n- **Objectif** : Moins d'un jour\n- **Calcul** : Temps moyen pour tous les changements\n- **Étapes pratiques** : 1. Utiliser des outils comme GitHub Actions ou Jenkins pour la journalisation automatisée 2. Identifier les retards dans les étapes de revue, de test ou d'approbation 3. Automatiser autant que possible pour réduire les goulots d'étranglement humains",{"data":240,"type":217},{"text":241},"### 3. Taux d'échec des changements\nPourcentage de déploiements causant des défaillances en production.\n- **Objectif** : 0-15%\n- **Calcul** : (Changements échoués \u002F Total des changements) × 100\n- **Étapes pratiques** : 1. Définir « échec » (ex. : rollback, hotfix, service dégradé >1h) 2. Implémenter des déploiements canary et des feature flags 3. Réaliser des post-mortems sur les échecs",{"data":243,"type":217},{"text":244},"### 4. Temps moyen de récupération (MTTR)\nTemps moyen pour restaurer le service après une défaillance.\n- **Objectif** : Moins d'une heure\n- **Calcul** : Temps d'arrêt total \u002F Nombre d'incidents\n- **Étapes pratiques** : 1. Configurer des alertes avec PagerDuty ou Opsgenie 2. Automatiser les procédures de rollback 3. Exécuter des exercices d'ingénierie du chaos",{"data":246,"type":217},{"text":247},"## Métriques clés de gestion du changement",{"data":249,"type":217},{"text":250},"### 1. Taux de succès des changements\nProportion des changements mis en œuvre sans problèmes.\n- **Objectif** : >85%\n- **Calcul** : (Changements réussis \u002F Total des changements) × 100\n- **Étapes pratiques** : 1. Standardiser les modèles de demande de changement 2. Exiger des évaluations des risques et des revues par les pairs 3. Suivre via des outils ITSM comme ServiceNow",{"data":252,"type":217},{"text":253},"### 2. Volume de changements et arriéré\nNombre de changements traités vs. en attente.\n- **Objectif** : Arriéré \u003C10% du volume mensuel\n- **Calcul** : Changements en attente \u002F Total soumis\n- **Étapes pratiques** : 1. Prioriser en utilisant la méthode MoSCoW 2. Mettre en place des comités consultatifs sur les changements (CAB) 3. Surveiller le temps de cycle de la demande à l'approbation",{"data":255,"type":217},{"text":256},"### 3. Pourcentage de changements d'urgence\nRatio des changements urgents par rapport au total des changements.\n- **Objectif** : \u003C10%\n- **Calcul** : (Changements d'urgence \u002F Total) × 100\n- **Étapes pratiques** : 1. Analyser les causes profondes des urgences 2. Passer à une maintenance proactive 3. Appliquer des revues post-changement",{"data":258,"type":217},{"text":259},"## Métriques de réalisation de la valeur",{"data":261,"type":217},{"text":262},"### 1. Valeur métier livrée\nQuantifie l'impact des changements sur les résultats clés.\n- **Exemples** : Augmentation des revenus, économies de coûts, engagement des utilisateurs\n- **Calcul** : Delta des KPI avant\u002Faprès le changement\n- **Étapes pratiques** : 1. Étiqueter les changements avec les résultats métier attendus 2. Utiliser des frameworks OKR pour l'alignement 3. Produire des tableaux de bord trimestriels de la valeur",{"data":264,"type":217},{"text":265},"### 2. Satisfaction client (CSAT)\nRetours sur les changements livrés.\n- **Objectif** : >4\u002F5\n- **Calcul** : Note moyenne des enquêtes post-déploiement\n- **Étapes pratiques** : 1. Automatiser les enquêtes NPS\u002FCSAT 2. Corréler avec les métriques de déploiement 3. Itérer en fonction des retours qualitatifs",{"data":267,"type":217},{"text":268},"## Mise en œuvre d'un cadre de métriques",{"data":270,"type":217},{"text":271},"1. **Sélectionner les métriques** : Commencez par les quatre métriques clés de DORA, puis ajoutez des métriques spécifiques aux changements.\n2. **Outils** : Utilisez des plateformes d'observabilité (Datadog, New Relic) intégrées à l'ITSM.\n3. **Tableaux de bord** : Créez des vues en temps réel dans Grafana ou Tableau.\n4. **Analyse comparative** : Comparez avec les pairs du secteur via le rapport Accelerate State of DevOps.\n5. **Rythme de revue** : Revues hebdomadaires par l'équipe, mises à jour mensuelles pour la direction.\n6. **Boucles d'action** : Reliez les métriques aux rétrospectives et à la planification PI.",{"data":273,"type":217},{"text":274},"## Pièges courants et bonnes pratiques",{"data":276,"type":217},{"text":277},"- **Piège** : Métriques de vanité (par ex. lignes de code) – Concentrez-vous sur les résultats.\n- **Bonne pratique** : Le contexte compte ; segmentez par équipe\u002Fservice.\n- **Piège** : Surcharge de métriques – Limitez-vous à 7-10 métriques principales.\n- **Bonne pratique** : Automatisez la collecte pour garantir l'exactitude.",{"data":279,"type":217},{"text":280},"Affinez régulièrement vos métriques pour refléter l'évolution des priorités. Pour réussir à l'échelle de l'entreprise, intégrez-les à vos modèles de référence pour la livraison et le changement.","2.31","Ce guide fournit un aperçu détaillé des métriques essentielles pour la livraison et la gestion du changement en entreprise, aidant les équipes à mesurer la performance, optimiser les processus et favoriser l'amélioration continue. Découvrez les indicateurs clés, les méthodes de calcul et les meilleures pratiques pour aligner vos métriques sur les résultats commerciaux.","\u002Fuploads\u002F2026\u002F06\u002Fmetrics-1781624416316-4nsuwg.webp","metrics-1781624416316-4nsuwg","PUBLISHED","2026-03-01T17:51:00.000Z","2026-03-01T18:51:22.389Z","2026-06-19T12:02:37.931Z",{"en":290,"de":291,"sr":292,"es":293,"fr":294,"it":295,"ru":296,"zh":297},"\u002Fblog\u002Fmetrics","\u002Fde\u002Fblog\u002Fmetrics","\u002Fsr\u002Fblog\u002Fmetrics","\u002Fes\u002Fblog\u002Fmetrics","\u002Ffr\u002Fblog\u002Fmetrics","\u002Fit\u002Fblog\u002Fmetrics","\u002Fru\u002Fblog\u002Fmetrics","\u002Fzh\u002Fblog\u002Fmetrics",[299],{"id":300,"name":301,"slug":209},50,"Métriques",{"id":303,"login":304,"email":305,"displayName":306},"20","rooth8233","","Aleksandar Stajić",[308,768],{"lang":309,"title":310,"content":311,"contentJson":312,"excerpt":767},"en","Comprehensive Metrics Guide for Delivery and Change Management","{\"time\":1781870516357,\"blocks\":[{\"id\":\"oj0-fAtlCh\",\"type\":\"header\",\"data\":{\"text\":\"Comprehensive Metrics Guide for Delivery and Change Management\",\"level\":2},\"tunes\":{}},{\"id\":\"ISjDiIjaeq\",\"type\":\"paragraph\",\"data\":{\"text\":\"In enterprise environments, effective delivery and change management rely on data-driven insights. Metrics serve as the foundation for assessing performance, identifying bottlenecks, and ensuring alignment with strategic goals. This guide covers core metrics across delivery pipelines, change processes, and overall value realization, with practical steps for implementation.\"},\"tunes\":{}},{\"id\":\"fRTle5vv6Z\",\"type\":\"header\",\"data\":{\"text\":\"Why Metrics Matter in Delivery and Change\",\"level\":2},\"tunes\":{}},{\"id\":\"HZ0SUWslsD\",\"type\":\"paragraph\",\"data\":{\"text\":\"Metrics transform subjective opinions into objective data, enabling teams to:\"},\"tunes\":{}},{\"id\":\"howitEC_8a\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"Track progress against objectives\",\"Predict and mitigate risks\",\"Optimize resource allocation\",\"Demonstrate ROI to stakeholders\"]},\"tunes\":{}},{\"id\":\"XW4uadE2pP\",\"type\":\"paragraph\",\"data\":{\"text\":\"Without robust metrics, organizations risk siloed efforts, prolonged downtimes, and failed transformations.\"},\"tunes\":{}},{\"id\":\"YFAZIH6dpy\",\"type\":\"header\",\"data\":{\"text\":\"Core Delivery Metrics\",\"level\":2},\"tunes\":{}},{\"id\":\"vPcGG7nWqk\",\"type\":\"header\",\"data\":{\"text\":\"1. Deployment Frequency\",\"level\":3},\"tunes\":{}},{\"id\":\"j0znRWC37o\",\"type\":\"paragraph\",\"data\":{\"text\":\"Measures how often code is deployed to production.\"},\"tunes\":{}},{\"id\":\"0Q_por0qd8\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> Daily or multiple times per day for elite performers (DORA standards)\",\"\u003Cb>Calculation:\u003C\u002Fb> Number of deployments per day\u002Fweek\u002Fmonth\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Integrate deployment tracking into your CI\u002FCD pipeline; segment by environment (dev\u002Fstaging\u002Fprod); benchmark against industry standards\"]},\"tunes\":{}},{\"id\":\"3v0GYLfadV\",\"type\":\"header\",\"data\":{\"text\":\"2. Lead Time for Changes\",\"level\":3},\"tunes\":{}},{\"id\":\"3kN4Iql0xW\",\"type\":\"paragraph\",\"data\":{\"text\":\"Time from commit to production deployment.\"},\"tunes\":{}},{\"id\":\"TN8KK4oQGb\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> Less than one day\",\"\u003Cb>Calculation:\u003C\u002Fb> Average time across all changes\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Use tools like GitHub Actions or Jenkins for automated logging; identify delays in review, testing, or approval stages; automate where possible to reduce human bottlenecks\"]},\"tunes\":{}},{\"id\":\"hhT1FskeYJ\",\"type\":\"header\",\"data\":{\"text\":\"3. Change Failure Rate\",\"level\":3},\"tunes\":{}},{\"id\":\"Kv9rEzxtNu\",\"type\":\"paragraph\",\"data\":{\"text\":\"Percentage of deployments causing failures in production.\"},\"tunes\":{}},{\"id\":\"9QKJ30UKfC\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> 0–15%\",\"\u003Cb>Calculation:\u003C\u002Fb> (Failed changes \u002F Total changes) × 100\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Define “failure” such as rollback, hotfix, or degraded service >1hr; implement canary releases and feature flags; conduct post-mortems on failures\"]},\"tunes\":{}},{\"id\":\"wqmNrB5Sl2\",\"type\":\"header\",\"data\":{\"text\":\"4. Mean Time to Recovery (MTTR)\",\"level\":3},\"tunes\":{}},{\"id\":\"RqPfsrrRVf\",\"type\":\"paragraph\",\"data\":{\"text\":\"Average time to restore service after a failure.\"},\"tunes\":{}},{\"id\":\"tasrkYwdlC\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> Less than one hour\",\"\u003Cb>Calculation:\u003C\u002Fb> Total downtime \u002F Number of incidents\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Set up alerting with PagerDuty or Opsgenie; automate rollback procedures; run chaos engineering drills\"]},\"tunes\":{}},{\"id\":\"Je-aH7vPRX\",\"type\":\"header\",\"data\":{\"text\":\"Key Change Management Metrics\",\"level\":2},\"tunes\":{}},{\"id\":\"Kf6s3F-oZs\",\"type\":\"header\",\"data\":{\"text\":\"1. Change Success Rate\",\"level\":3},\"tunes\":{}},{\"id\":\"nNzr1qvQpe\",\"type\":\"paragraph\",\"data\":{\"text\":\"Proportion of changes implemented without issues.\"},\"tunes\":{}},{\"id\":\"uZkCcs-YA8\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> >85%\",\"\u003Cb>Calculation:\u003C\u002Fb> (Successful changes \u002F Total changes) × 100\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Standardize change request templates; require risk assessments and peer reviews; track via ITSM tools like ServiceNow\"]},\"tunes\":{}},{\"id\":\"ZWXemWA64r\",\"type\":\"header\",\"data\":{\"text\":\"2. Change Volume and Backlog\",\"level\":3},\"tunes\":{}},{\"id\":\"MrEhXiOrXw\",\"type\":\"paragraph\",\"data\":{\"text\":\"Number of changes processed vs. pending.\"},\"tunes\":{}},{\"id\":\"55V65WsG7K\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> Backlog <10% of monthly volume\",\"\u003Cb>Calculation:\u003C\u002Fb> Pending changes \u002F Total submitted\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Prioritize using the MoSCoW method; implement change advisory boards (CAB); monitor cycle time from request to approval\"]},\"tunes\":{}},{\"id\":\"pACMNc-Zkb\",\"type\":\"header\",\"data\":{\"text\":\"3. Emergency Change Percentage\",\"level\":3},\"tunes\":{}},{\"id\":\"7hCu5ufa2r\",\"type\":\"paragraph\",\"data\":{\"text\":\"Ratio of urgent changes to total changes.\"},\"tunes\":{}},{\"id\":\"g18yGxVICg\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> <10%\",\"\u003Cb>Calculation:\u003C\u002Fb> (Emergency changes \u002F Total) × 100\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Analyze root causes of emergencies; shift to proactive maintenance; enforce post-change reviews\"]},\"tunes\":{}},{\"id\":\"W2YtQCmDLs\",\"type\":\"header\",\"data\":{\"text\":\"Value Realization Metrics\",\"level\":2},\"tunes\":{}},{\"id\":\"P_tyVQ4CjM\",\"type\":\"header\",\"data\":{\"text\":\"1. Business Value Delivered\",\"level\":3},\"tunes\":{}},{\"id\":\"r0uz2tAPEC\",\"type\":\"paragraph\",\"data\":{\"text\":\"Quantifies impact of changes on key outcomes.\"},\"tunes\":{}},{\"id\":\"e_Pj8XZbIC\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Examples:\u003C\u002Fb> Revenue uplift, cost savings, user engagement\",\"\u003Cb>Calculation:\u003C\u002Fb> Pre\u002Fpost change KPIs delta\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Tag changes with expected business outcomes; use OKR frameworks for alignment; report quarterly value scorecards\"]},\"tunes\":{}},{\"id\":\"qcwbaaPDb4\",\"type\":\"header\",\"data\":{\"text\":\"2. Customer Satisfaction (CSAT)\",\"level\":3},\"tunes\":{}},{\"id\":\"rrwOIY0gtF\",\"type\":\"paragraph\",\"data\":{\"text\":\"Feedback on delivered changes.\"},\"tunes\":{}},{\"id\":\"c5UgD9sSZ-\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> >4\u002F5 score\",\"\u003Cb>Calculation:\u003C\u002Fb> Average post-deployment survey score\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Automate NPS\u002FCSAT surveys; correlate with deployment metrics; iterate based on qualitative feedback\"]},\"tunes\":{}},{\"id\":\"t3hrEttpGF\",\"type\":\"header\",\"data\":{\"text\":\"Implementing a Metrics Framework\",\"level\":2},\"tunes\":{}},{\"id\":\"hkII1FWPa7\",\"type\":\"list\",\"data\":{\"style\":\"ordered\",\"meta\":{\"counterType\":\"numeric\"},\"items\":[\"\u003Cb>Select Metrics:\u003C\u002Fb> Start with DORA’s four key metrics, then add change-specific ones.\",\"\u003Cb>Tooling:\u003C\u002Fb> Use observability platforms such as Datadog or New Relic integrated with ITSM.\",\"\u003Cb>Dashboards:\u003C\u002Fb> Build real-time views in Grafana or Tableau.\",\"\u003Cb>Benchmarking:\u003C\u002Fb> Compare against industry peers via the Accelerate State of DevOps report.\",\"\u003Cb>Review Cadence:\u003C\u002Fb> Weekly team reviews and monthly leadership updates.\",\"\u003Cb>Action Loops:\u003C\u002Fb> Tie metrics to retrospectives and PI planning.\"]},\"tunes\":{}},{\"id\":\"dRPhe5XN-4\",\"type\":\"header\",\"data\":{\"text\":\"Common Pitfalls and Best Practices\",\"level\":2},\"tunes\":{}},{\"id\":\"EVW_cVDwDU\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Pitfall:\u003C\u002Fb> Vanity metrics such as lines of code — focus on outcomes.\",\"\u003Cb>Best Practice:\u003C\u002Fb> Context matters; segment by team\u002Fservice.\",\"\u003Cb>Pitfall:\u003C\u002Fb> Overloading with metrics — limit to 7–10 core ones.\",\"\u003Cb>Best Practice:\u003C\u002Fb> Automate collection to ensure accuracy.\"]},\"tunes\":{}},{\"id\":\"C23mLGuxd5\",\"type\":\"paragraph\",\"data\":{\"text\":\"Regularly refine your metrics to reflect evolving priorities. For enterprise-scale success, integrate these into your reference models for delivery and change.\"},\"tunes\":{}},{\"id\":\"VXW6drMjo9\",\"type\":\"header\",\"data\":{\"text\":\"Comprehensive Metrics Guide for Delivery and Change Management\",\"level\":1},\"tunes\":{}},{\"id\":\"1rknh3t2Y9\",\"type\":\"paragraph\",\"data\":{\"text\":\"In enterprise environments, effective delivery and change management rely on data-driven insights. Metrics serve as the foundation for assessing performance, identifying bottlenecks, and ensuring alignment with strategic goals. This guide covers core metrics across delivery pipelines, change processes, and overall value realization, with practical steps for implementation.\"},\"tunes\":{}},{\"id\":\"wur1ZgV-qz\",\"type\":\"header\",\"data\":{\"text\":\"Why Metrics Matter in Delivery and Change\",\"level\":2},\"tunes\":{}},{\"id\":\"fEe8WDFCXL\",\"type\":\"paragraph\",\"data\":{\"text\":\"Metrics transform subjective opinions into objective data, enabling teams to:\"},\"tunes\":{}},{\"id\":\"cXK-oYQgg4\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"Track progress against objectives\",\"Predict and mitigate risks\",\"Optimize resource allocation\",\"Demonstrate ROI to stakeholders\"]},\"tunes\":{}},{\"id\":\"gYkjIZd7xN\",\"type\":\"paragraph\",\"data\":{\"text\":\"Without robust metrics, organizations risk siloed efforts, prolonged downtimes, and failed transformations.\"},\"tunes\":{}},{\"id\":\"3qIHNPMkcD\",\"type\":\"header\",\"data\":{\"text\":\"Core Delivery Metrics\",\"level\":2},\"tunes\":{}},{\"id\":\"1w0BtZfmqQ\",\"type\":\"header\",\"data\":{\"text\":\"1. Deployment Frequency\",\"level\":3},\"tunes\":{}},{\"id\":\"aILaskrll-\",\"type\":\"paragraph\",\"data\":{\"text\":\"Measures how often code is deployed to production.\"},\"tunes\":{}},{\"id\":\"rWJQiVFOBF\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> Daily or multiple times per day for elite performers (DORA standards)\",\"\u003Cb>Calculation:\u003C\u002Fb> Number of deployments per day\u002Fweek\u002Fmonth\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Integrate deployment tracking into your CI\u002FCD pipeline; segment by environment (dev\u002Fstaging\u002Fprod); benchmark against industry standards\"]},\"tunes\":{}},{\"id\":\"VdC9OQJwpD\",\"type\":\"header\",\"data\":{\"text\":\"2. Lead Time for Changes\",\"level\":3},\"tunes\":{}},{\"id\":\"XEA7yc43HE\",\"type\":\"paragraph\",\"data\":{\"text\":\"Time from commit to production deployment.\"},\"tunes\":{}},{\"id\":\"xGdB85YJlk\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> Less than one day\",\"\u003Cb>Calculation:\u003C\u002Fb> Average time across all changes\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Use tools like GitHub Actions or Jenkins for automated logging; identify delays in review, testing, or approval stages; automate where possible to reduce human bottlenecks\"]},\"tunes\":{}},{\"id\":\"PWbBDRDN2W\",\"type\":\"header\",\"data\":{\"text\":\"3. Change Failure Rate\",\"level\":3},\"tunes\":{}},{\"id\":\"Q64M3tXFbM\",\"type\":\"paragraph\",\"data\":{\"text\":\"Percentage of deployments causing failures in production.\"},\"tunes\":{}},{\"id\":\"N5olZdBGbs\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> 0–15%\",\"\u003Cb>Calculation:\u003C\u002Fb> (Failed changes \u002F Total changes) × 100\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Define “failure” such as rollback, hotfix, or degraded service >1hr; implement canary releases and feature flags; conduct post-mortems on failures\"]},\"tunes\":{}},{\"id\":\"ely6c6RkEx\",\"type\":\"header\",\"data\":{\"text\":\"4. Mean Time to Recovery (MTTR)\",\"level\":3},\"tunes\":{}},{\"id\":\"8lTjIlskZv\",\"type\":\"paragraph\",\"data\":{\"text\":\"Average time to restore service after a failure.\"},\"tunes\":{}},{\"id\":\"RW4iDZQIz4\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> Less than one hour\",\"\u003Cb>Calculation:\u003C\u002Fb> Total downtime \u002F Number of incidents\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Set up alerting with PagerDuty or Opsgenie; automate rollback procedures; run chaos engineering drills\"]},\"tunes\":{}},{\"id\":\"8B0i9MhYER\",\"type\":\"header\",\"data\":{\"text\":\"Key Change Management Metrics\",\"level\":2},\"tunes\":{}},{\"id\":\"rjA490V5wf\",\"type\":\"header\",\"data\":{\"text\":\"1. Change Success Rate\",\"level\":3},\"tunes\":{}},{\"id\":\"XpFgLbKzQi\",\"type\":\"paragraph\",\"data\":{\"text\":\"Proportion of changes implemented without issues.\"},\"tunes\":{}},{\"id\":\"xEdffF97Nf\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> >85%\",\"\u003Cb>Calculation:\u003C\u002Fb> (Successful changes \u002F Total changes) × 100\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Standardize change request templates; require risk assessments and peer reviews; track via ITSM tools like ServiceNow\"]},\"tunes\":{}},{\"id\":\"mNi4vEbBku\",\"type\":\"header\",\"data\":{\"text\":\"2. Change Volume and Backlog\",\"level\":3},\"tunes\":{}},{\"id\":\"ue9YU7Uimc\",\"type\":\"paragraph\",\"data\":{\"text\":\"Number of changes processed vs. pending.\"},\"tunes\":{}},{\"id\":\"Z1n3CZvjaD\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> Backlog <10% of monthly volume\",\"\u003Cb>Calculation:\u003C\u002Fb> Pending changes \u002F Total submitted\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Prioritize using the MoSCoW method; implement change advisory boards (CAB); monitor cycle time from request to approval\"]},\"tunes\":{}},{\"id\":\"I1x-Ey-mfd\",\"type\":\"header\",\"data\":{\"text\":\"3. Emergency Change Percentage\",\"level\":3},\"tunes\":{}},{\"id\":\"45knEUxyEF\",\"type\":\"paragraph\",\"data\":{\"text\":\"Ratio of urgent changes to total changes.\"},\"tunes\":{}},{\"id\":\"tRaJFhjhmS\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> <10%\",\"\u003Cb>Calculation:\u003C\u002Fb> (Emergency changes \u002F Total) × 100\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Analyze root causes of emergencies; shift to proactive maintenance; enforce post-change reviews\"]},\"tunes\":{}},{\"id\":\"oV5kZqUCIL\",\"type\":\"header\",\"data\":{\"text\":\"Value Realization Metrics\",\"level\":2},\"tunes\":{}},{\"id\":\"4hNKwp_PF1\",\"type\":\"header\",\"data\":{\"text\":\"1. Business Value Delivered\",\"level\":3},\"tunes\":{}},{\"id\":\"iv-4nKxGFx\",\"type\":\"paragraph\",\"data\":{\"text\":\"Quantifies impact of changes on key outcomes.\"},\"tunes\":{}},{\"id\":\"pZAJIihqZV\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Examples:\u003C\u002Fb> Revenue uplift, cost savings, user engagement\",\"\u003Cb>Calculation:\u003C\u002Fb> Pre\u002Fpost change KPIs delta\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Tag changes with expected business outcomes; use OKR frameworks for alignment; report quarterly value scorecards\"]},\"tunes\":{}},{\"id\":\"NC5RdYT9RD\",\"type\":\"header\",\"data\":{\"text\":\"2. Customer Satisfaction (CSAT)\",\"level\":3},\"tunes\":{}},{\"id\":\"oTKVOfzqKz\",\"type\":\"paragraph\",\"data\":{\"text\":\"Feedback on delivered changes.\"},\"tunes\":{}},{\"id\":\"kQdagmD0wy\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Target:\u003C\u002Fb> >4\u002F5 score\",\"\u003Cb>Calculation:\u003C\u002Fb> Average post-deployment survey score\",\"\u003Cb>Practical Steps:\u003C\u002Fb> Automate NPS\u002FCSAT surveys; correlate with deployment metrics; iterate based on qualitative feedback\"]},\"tunes\":{}},{\"id\":\"1koeukp92j\",\"type\":\"header\",\"data\":{\"text\":\"Implementing a Metrics Framework\",\"level\":2},\"tunes\":{}},{\"id\":\"DzssiiCkc4\",\"type\":\"list\",\"data\":{\"style\":\"ordered\",\"meta\":{\"counterType\":\"numeric\"},\"items\":[\"\u003Cb>Select Metrics:\u003C\u002Fb> Start with DORA’s four key metrics, then add change-specific ones.\",\"\u003Cb>Tooling:\u003C\u002Fb> Use observability platforms such as Datadog or New Relic integrated with ITSM.\",\"\u003Cb>Dashboards:\u003C\u002Fb> Build real-time views in Grafana or Tableau.\",\"\u003Cb>Benchmarking:\u003C\u002Fb> Compare against industry peers via the Accelerate State of DevOps report.\",\"\u003Cb>Review Cadence:\u003C\u002Fb> Weekly team reviews and monthly leadership updates.\",\"\u003Cb>Action Loops:\u003C\u002Fb> Tie metrics to retrospectives and PI planning.\"]},\"tunes\":{}},{\"id\":\"M2UT1qUCLy\",\"type\":\"header\",\"data\":{\"text\":\"Common Pitfalls and Best Practices\",\"level\":2},\"tunes\":{}},{\"id\":\"VUrYC08F-D\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"\u003Cb>Pitfall:\u003C\u002Fb> Vanity metrics such as lines of code — focus on outcomes.\",\"\u003Cb>Best Practice:\u003C\u002Fb> Context matters; segment by team\u002Fservice.\",\"\u003Cb>Pitfall:\u003C\u002Fb> Overloading with metrics — limit to 7–10 core ones.\",\"\u003Cb>Best Practice:\u003C\u002Fb> Automate collection to ensure accuracy.\"]},\"tunes\":{}},{\"id\":\"bhwVlAzXlD\",\"type\":\"paragraph\",\"data\":{\"text\":\"Regularly refine your metrics to reflect evolving priorities. For enterprise-scale success, integrate these into your reference models for delivery and change.\"},\"tunes\":{}}],\"version\":\"2.31.5\"}",{"time":313,"blocks":314,"version":766},1781870516357,[315,320,325,330,335,347,352,357,363,368,377,382,387,396,401,406,415,420,425,434,439,444,449,458,463,468,477,482,487,496,501,506,511,520,525,530,539,544,558,563,573,578,582,586,590,594,600,604,608,612,616,622,626,630,636,640,644,650,654,658,664,668,672,676,682,686,690,696,700,704,710,714,718,722,728,732,736,742,746,752,756,762],{"id":316,"data":317,"type":42,"tunes":319},"oj0-fAtlCh",{"text":310,"level":318},2,{},{"id":321,"data":322,"type":217,"tunes":324},"ISjDiIjaeq",{"text":323},"In enterprise environments, effective delivery and change management rely on data-driven insights. Metrics serve as the foundation for assessing performance, identifying bottlenecks, and ensuring alignment with strategic goals. This guide covers core metrics across delivery pipelines, change processes, and overall value realization, with practical steps for implementation.",{},{"id":326,"data":327,"type":42,"tunes":329},"fRTle5vv6Z",{"text":328,"level":318},"Why Metrics Matter in Delivery and Change",{},{"id":331,"data":332,"type":217,"tunes":334},"HZ0SUWslsD",{"text":333},"Metrics transform subjective opinions into objective data, enabling teams to:",{},{"id":336,"data":337,"type":345,"tunes":346},"howitEC_8a",{"meta":338,"items":339,"style":344},{},[340,341,342,343],"Track progress against objectives","Predict and mitigate risks","Optimize resource allocation","Demonstrate ROI to stakeholders","unordered","list",{},{"id":348,"data":349,"type":217,"tunes":351},"XW4uadE2pP",{"text":350},"Without robust metrics, organizations risk siloed efforts, prolonged downtimes, and failed transformations.",{},{"id":353,"data":354,"type":42,"tunes":356},"YFAZIH6dpy",{"text":355,"level":318},"Core Delivery Metrics",{},{"id":358,"data":359,"type":42,"tunes":362},"vPcGG7nWqk",{"text":360,"level":361},"1. Deployment Frequency",3,{},{"id":364,"data":365,"type":217,"tunes":367},"j0znRWC37o",{"text":366},"Measures how often code is deployed to production.",{},{"id":369,"data":370,"type":345,"tunes":376},"0Q_por0qd8",{"meta":371,"items":372,"style":344},{},[373,374,375],"\u003Cb>Target:\u003C\u002Fb> Daily or multiple times per day for elite performers (DORA standards)","\u003Cb>Calculation:\u003C\u002Fb> Number of deployments per day\u002Fweek\u002Fmonth","\u003Cb>Practical Steps:\u003C\u002Fb> Integrate deployment tracking into your CI\u002FCD pipeline; segment by environment (dev\u002Fstaging\u002Fprod); benchmark against industry standards",{},{"id":378,"data":379,"type":42,"tunes":381},"3v0GYLfadV",{"text":380,"level":361},"2. Lead Time for Changes",{},{"id":383,"data":384,"type":217,"tunes":386},"3kN4Iql0xW",{"text":385},"Time from commit to production deployment.",{},{"id":388,"data":389,"type":345,"tunes":395},"TN8KK4oQGb",{"meta":390,"items":391,"style":344},{},[392,393,394],"\u003Cb>Target:\u003C\u002Fb> Less than one day","\u003Cb>Calculation:\u003C\u002Fb> Average time across all changes","\u003Cb>Practical Steps:\u003C\u002Fb> Use tools like GitHub Actions or Jenkins for automated logging; identify delays in review, testing, or approval stages; automate where possible to reduce human bottlenecks",{},{"id":397,"data":398,"type":42,"tunes":400},"hhT1FskeYJ",{"text":399,"level":361},"3. Change Failure Rate",{},{"id":402,"data":403,"type":217,"tunes":405},"Kv9rEzxtNu",{"text":404},"Percentage of deployments causing failures in production.",{},{"id":407,"data":408,"type":345,"tunes":414},"9QKJ30UKfC",{"meta":409,"items":410,"style":344},{},[411,412,413],"\u003Cb>Target:\u003C\u002Fb> 0–15%","\u003Cb>Calculation:\u003C\u002Fb> (Failed changes \u002F Total changes) × 100","\u003Cb>Practical Steps:\u003C\u002Fb> Define “failure” such as rollback, hotfix, or degraded service >1hr; implement canary releases and feature flags; conduct post-mortems on failures",{},{"id":416,"data":417,"type":42,"tunes":419},"wqmNrB5Sl2",{"text":418,"level":361},"4. Mean Time to Recovery (MTTR)",{},{"id":421,"data":422,"type":217,"tunes":424},"RqPfsrrRVf",{"text":423},"Average time to restore service after a failure.",{},{"id":426,"data":427,"type":345,"tunes":433},"tasrkYwdlC",{"meta":428,"items":429,"style":344},{},[430,431,432],"\u003Cb>Target:\u003C\u002Fb> Less than one hour","\u003Cb>Calculation:\u003C\u002Fb> Total downtime \u002F Number of incidents","\u003Cb>Practical Steps:\u003C\u002Fb> Set up alerting with PagerDuty or Opsgenie; automate rollback procedures; run chaos engineering drills",{},{"id":435,"data":436,"type":42,"tunes":438},"Je-aH7vPRX",{"text":437,"level":318},"Key Change Management Metrics",{},{"id":440,"data":441,"type":42,"tunes":443},"Kf6s3F-oZs",{"text":442,"level":361},"1. Change Success Rate",{},{"id":445,"data":446,"type":217,"tunes":448},"nNzr1qvQpe",{"text":447},"Proportion of changes implemented without issues.",{},{"id":450,"data":451,"type":345,"tunes":457},"uZkCcs-YA8",{"meta":452,"items":453,"style":344},{},[454,455,456],"\u003Cb>Target:\u003C\u002Fb> >85%","\u003Cb>Calculation:\u003C\u002Fb> (Successful changes \u002F Total changes) × 100","\u003Cb>Practical Steps:\u003C\u002Fb> Standardize change request templates; require risk assessments and peer reviews; track via ITSM tools like ServiceNow",{},{"id":459,"data":460,"type":42,"tunes":462},"ZWXemWA64r",{"text":461,"level":361},"2. Change Volume and Backlog",{},{"id":464,"data":465,"type":217,"tunes":467},"MrEhXiOrXw",{"text":466},"Number of changes processed vs. pending.",{},{"id":469,"data":470,"type":345,"tunes":476},"55V65WsG7K",{"meta":471,"items":472,"style":344},{},[473,474,475],"\u003Cb>Target:\u003C\u002Fb> Backlog <10% of monthly volume","\u003Cb>Calculation:\u003C\u002Fb> Pending changes \u002F Total submitted","\u003Cb>Practical Steps:\u003C\u002Fb> Prioritize using the MoSCoW method; implement change advisory boards (CAB); monitor cycle time from request to approval",{},{"id":478,"data":479,"type":42,"tunes":481},"pACMNc-Zkb",{"text":480,"level":361},"3. Emergency Change Percentage",{},{"id":483,"data":484,"type":217,"tunes":486},"7hCu5ufa2r",{"text":485},"Ratio of urgent changes to total changes.",{},{"id":488,"data":489,"type":345,"tunes":495},"g18yGxVICg",{"meta":490,"items":491,"style":344},{},[492,493,494],"\u003Cb>Target:\u003C\u002Fb> <10%","\u003Cb>Calculation:\u003C\u002Fb> (Emergency changes \u002F Total) × 100","\u003Cb>Practical Steps:\u003C\u002Fb> Analyze root causes of emergencies; shift to proactive maintenance; enforce post-change reviews",{},{"id":497,"data":498,"type":42,"tunes":500},"W2YtQCmDLs",{"text":499,"level":318},"Value Realization Metrics",{},{"id":502,"data":503,"type":42,"tunes":505},"P_tyVQ4CjM",{"text":504,"level":361},"1. Business Value Delivered",{},{"id":507,"data":508,"type":217,"tunes":510},"r0uz2tAPEC",{"text":509},"Quantifies impact of changes on key outcomes.",{},{"id":512,"data":513,"type":345,"tunes":519},"e_Pj8XZbIC",{"meta":514,"items":515,"style":344},{},[516,517,518],"\u003Cb>Examples:\u003C\u002Fb> Revenue uplift, cost savings, user engagement","\u003Cb>Calculation:\u003C\u002Fb> Pre\u002Fpost change KPIs delta","\u003Cb>Practical Steps:\u003C\u002Fb> Tag changes with expected business outcomes; use OKR frameworks for alignment; report quarterly value scorecards",{},{"id":521,"data":522,"type":42,"tunes":524},"qcwbaaPDb4",{"text":523,"level":361},"2. Customer Satisfaction (CSAT)",{},{"id":526,"data":527,"type":217,"tunes":529},"rrwOIY0gtF",{"text":528},"Feedback on delivered changes.",{},{"id":531,"data":532,"type":345,"tunes":538},"c5UgD9sSZ-",{"meta":533,"items":534,"style":344},{},[535,536,537],"\u003Cb>Target:\u003C\u002Fb> >4\u002F5 score","\u003Cb>Calculation:\u003C\u002Fb> Average post-deployment survey score","\u003Cb>Practical Steps:\u003C\u002Fb> Automate NPS\u002FCSAT surveys; correlate with deployment metrics; iterate based on qualitative feedback",{},{"id":540,"data":541,"type":42,"tunes":543},"t3hrEttpGF",{"text":542,"level":318},"Implementing a Metrics Framework",{},{"id":545,"data":546,"type":345,"tunes":557},"hkII1FWPa7",{"meta":547,"items":549,"style":556},{"counterType":548},"numeric",[550,551,552,553,554,555],"\u003Cb>Select Metrics:\u003C\u002Fb> Start with DORA’s four key metrics, then add change-specific ones.","\u003Cb>Tooling:\u003C\u002Fb> Use observability platforms such as Datadog or New Relic integrated with ITSM.","\u003Cb>Dashboards:\u003C\u002Fb> Build real-time views in Grafana or Tableau.","\u003Cb>Benchmarking:\u003C\u002Fb> Compare against industry peers via the Accelerate State of DevOps report.","\u003Cb>Review Cadence:\u003C\u002Fb> Weekly team reviews and monthly leadership updates.","\u003Cb>Action Loops:\u003C\u002Fb> Tie metrics to retrospectives and PI planning.","ordered",{},{"id":559,"data":560,"type":42,"tunes":562},"dRPhe5XN-4",{"text":561,"level":318},"Common Pitfalls and Best Practices",{},{"id":564,"data":565,"type":345,"tunes":572},"EVW_cVDwDU",{"meta":566,"items":567,"style":344},{},[568,569,570,571],"\u003Cb>Pitfall:\u003C\u002Fb> Vanity metrics such as lines of code — focus on outcomes.","\u003Cb>Best Practice:\u003C\u002Fb> Context matters; segment by team\u002Fservice.","\u003Cb>Pitfall:\u003C\u002Fb> Overloading with metrics — limit to 7–10 core ones.","\u003Cb>Best Practice:\u003C\u002Fb> Automate collection to ensure accuracy.",{},{"id":574,"data":575,"type":217,"tunes":577},"C23mLGuxd5",{"text":576},"Regularly refine your metrics to reflect evolving priorities. For enterprise-scale success, integrate these into your reference models for delivery and change.",{},{"id":579,"data":580,"type":42,"tunes":581},"VXW6drMjo9",{"text":310,"level":40},{},{"id":583,"data":584,"type":217,"tunes":585},"1rknh3t2Y9",{"text":323},{},{"id":587,"data":588,"type":42,"tunes":589},"wur1ZgV-qz",{"text":328,"level":318},{},{"id":591,"data":592,"type":217,"tunes":593},"fEe8WDFCXL",{"text":333},{},{"id":595,"data":596,"type":345,"tunes":599},"cXK-oYQgg4",{"meta":597,"items":598,"style":344},{},[340,341,342,343],{},{"id":601,"data":602,"type":217,"tunes":603},"gYkjIZd7xN",{"text":350},{},{"id":605,"data":606,"type":42,"tunes":607},"3qIHNPMkcD",{"text":355,"level":318},{},{"id":609,"data":610,"type":42,"tunes":611},"1w0BtZfmqQ",{"text":360,"level":361},{},{"id":613,"data":614,"type":217,"tunes":615},"aILaskrll-",{"text":366},{},{"id":617,"data":618,"type":345,"tunes":621},"rWJQiVFOBF",{"meta":619,"items":620,"style":344},{},[373,374,375],{},{"id":623,"data":624,"type":42,"tunes":625},"VdC9OQJwpD",{"text":380,"level":361},{},{"id":627,"data":628,"type":217,"tunes":629},"XEA7yc43HE",{"text":385},{},{"id":631,"data":632,"type":345,"tunes":635},"xGdB85YJlk",{"meta":633,"items":634,"style":344},{},[392,393,394],{},{"id":637,"data":638,"type":42,"tunes":639},"PWbBDRDN2W",{"text":399,"level":361},{},{"id":641,"data":642,"type":217,"tunes":643},"Q64M3tXFbM",{"text":404},{},{"id":645,"data":646,"type":345,"tunes":649},"N5olZdBGbs",{"meta":647,"items":648,"style":344},{},[411,412,413],{},{"id":651,"data":652,"type":42,"tunes":653},"ely6c6RkEx",{"text":418,"level":361},{},{"id":655,"data":656,"type":217,"tunes":657},"8lTjIlskZv",{"text":423},{},{"id":659,"data":660,"type":345,"tunes":663},"RW4iDZQIz4",{"meta":661,"items":662,"style":344},{},[430,431,432],{},{"id":665,"data":666,"type":42,"tunes":667},"8B0i9MhYER",{"text":437,"level":318},{},{"id":669,"data":670,"type":42,"tunes":671},"rjA490V5wf",{"text":442,"level":361},{},{"id":673,"data":674,"type":217,"tunes":675},"XpFgLbKzQi",{"text":447},{},{"id":677,"data":678,"type":345,"tunes":681},"xEdffF97Nf",{"meta":679,"items":680,"style":344},{},[454,455,456],{},{"id":683,"data":684,"type":42,"tunes":685},"mNi4vEbBku",{"text":461,"level":361},{},{"id":687,"data":688,"type":217,"tunes":689},"ue9YU7Uimc",{"text":466},{},{"id":691,"data":692,"type":345,"tunes":695},"Z1n3CZvjaD",{"meta":693,"items":694,"style":344},{},[473,474,475],{},{"id":697,"data":698,"type":42,"tunes":699},"I1x-Ey-mfd",{"text":480,"level":361},{},{"id":701,"data":702,"type":217,"tunes":703},"45knEUxyEF",{"text":485},{},{"id":705,"data":706,"type":345,"tunes":709},"tRaJFhjhmS",{"meta":707,"items":708,"style":344},{},[492,493,494],{},{"id":711,"data":712,"type":42,"tunes":713},"oV5kZqUCIL",{"text":499,"level":318},{},{"id":715,"data":716,"type":42,"tunes":717},"4hNKwp_PF1",{"text":504,"level":361},{},{"id":719,"data":720,"type":217,"tunes":721},"iv-4nKxGFx",{"text":509},{},{"id":723,"data":724,"type":345,"tunes":727},"pZAJIihqZV",{"meta":725,"items":726,"style":344},{},[516,517,518],{},{"id":729,"data":730,"type":42,"tunes":731},"NC5RdYT9RD",{"text":523,"level":361},{},{"id":733,"data":734,"type":217,"tunes":735},"oTKVOfzqKz",{"text":528},{},{"id":737,"data":738,"type":345,"tunes":741},"kQdagmD0wy",{"meta":739,"items":740,"style":344},{},[535,536,537],{},{"id":743,"data":744,"type":42,"tunes":745},"1koeukp92j",{"text":542,"level":318},{},{"id":747,"data":748,"type":345,"tunes":751},"DzssiiCkc4",{"meta":749,"items":750,"style":556},{"counterType":548},[550,551,552,553,554,555],{},{"id":753,"data":754,"type":42,"tunes":755},"M2UT1qUCLy",{"text":561,"level":318},{},{"id":757,"data":758,"type":345,"tunes":761},"VUrYC08F-D",{"meta":759,"items":760,"style":344},{},[568,569,570,571],{},{"id":763,"data":764,"type":217,"tunes":765},"bhwVlAzXlD",{"text":576},{},"2.31.5","This guide provides a detailed overview of essential metrics for enterprise delivery and change management, helping teams measure performance, optimize processes, and drive continuous improvement. Discover key indicators, calculation methods, and best practices to align your metrics with business outcomes.",{"lang":7,"title":208,"content":210,"contentJson":769,"excerpt":282},{"time":212,"blocks":770,"version":281},[771,773,775,777,779,781,783,785,787,789,791,793,795,797,799,801,803,805,807,809,811,813],{"data":772,"type":217},{"text":216},{"data":774,"type":217},{"text":220},{"data":776,"type":217},{"text":223},{"data":778,"type":217},{"text":226},{"data":780,"type":217},{"text":229},{"data":782,"type":217},{"text":232},{"data":784,"type":217},{"text":235},{"data":786,"type":217},{"text":238},{"data":788,"type":217},{"text":241},{"data":790,"type":217},{"text":244},{"data":792,"type":217},{"text":247},{"data":794,"type":217},{"text":250},{"data":796,"type":217},{"text":253},{"data":798,"type":217},{"text":256},{"data":800,"type":217},{"text":259},{"data":802,"type":217},{"text":262},{"data":804,"type":217},{"text":265},{"data":806,"type":217},{"text":268},{"data":808,"type":217},{"text":271},{"data":810,"type":217},{"text":274},{"data":812,"type":217},{"text":277},{"data":814,"type":217},{"text":280},"Post erfolgreich abgerufen",{"items":817,"source":902,"manualIds":903,"manualMatchedIds":904},[818,825,832,839,846,853,860,867,874,881,888,895],{"id":819,"slug":820,"title":821,"excerpt":822,"featuredImage":823,"publishedAt":824},"489","agentic-ai-explained-when-an-ai-system-can-plan-use-tools-and-act","L'IA agentique expliquée : quand un système d'IA peut planifier, utiliser des outils et agir","L'IA agentique utilise des modèles au sein de boucles d'exécution multi-étapes où ils peuvent choisir des outils, observer les résultats, mettre à jour l'état et adapter leur action suivante dans des limites explicites d'exécution et de permissions.","\u002Fuploads\u002F2026\u002F10\u002Fagentic-ai-explained-when-an-ai-system-can-plan-use-tools-and-act-1791481499084-wnji2a.webp","2026-10-08T11:43:00.000Z",{"id":826,"slug":827,"title":828,"excerpt":829,"featuredImage":830,"publishedAt":831},"485","enterprise-ai-architecture-what-changes-when-ai-enters-a-company","Architecture de l’IA en entreprise : ce qui change lorsque l’IA entre dans une entreprise","L'architecture de l'IA en entreprise explique comment l'IA transforme les systèmes d'entreprise à travers l'autorité des données, l'identité, les autorisations, les fournisseurs, les risques, la gouvernance, l'évaluation, la conformité et les opérations.","\u002Fuploads\u002F2026\u002F10\u002Fenterprise-ai-architecture-what-changes-when-ai-enters-a-company-1791478161363-czrwaq.webp","2026-10-08T10:48:00.000Z",{"id":833,"slug":834,"title":835,"excerpt":836,"featuredImage":837,"publishedAt":838},"465","from-research-protocol-to-a-general-ai-reasoning-framework","Du Protocole de Recherche à un Cadre Général de Raisonnement IA","Une méthodologie développée pour une recherche rigoureuse assistée par l'IA peut être généralisée bien au-delà de la recherche elle-même. En séparant les preuves des suppositions, en testant des hypothèses concurrentes, en contrôlant le cadrage des prompts, en recherchant des contre-preuves et en appliquant des validateurs spécifiques au domaine, la même architecture de raisonnement peut améliorer le débogage, la conception logicielle, la stratégie, l'analyse technique et l'aide à la décision assistée par l'IA.","\u002Fuploads\u002F2026\u002F09\u002Ffrom-research-protocol-to-a-general-ai-reasoning-framework-1789802635691-hhf78v.webp","2026-09-19T01:16:00.000Z",{"id":840,"slug":841,"title":842,"excerpt":843,"featuredImage":844,"publishedAt":845},"462","the-prompt-is-part-of-the-bias-how-ai-framing-shapes-reasoning","Le prompt fait partie du biais : comment le cadrage de l'IA façonne le raisonnement","La formulation d'un prompt n'est pas neutre. Explorez comment le cadrage, les présupposés, le suivi des instructions et la sycophancie peuvent façonner le raisonnement de l'IA—et pourquoi des conclusions fiables nécessitent des tests au-delà du prompt initial.","\u002Fuploads\u002F2026\u002F09\u002Fthe-prompt-is-part-of-the-bias-how-ai-framing-shapes-reasoning-1789804884054-u278vc.webp","2026-09-19T01:04:00.000Z",{"id":847,"slug":848,"title":849,"excerpt":850,"featuredImage":851,"publishedAt":852},"471","how-to-know-whether-an-ai-agent-actually-used-the-right-evidence","Comment savoir si un agent IA a réellement utilisé les bonnes preuves","Un agent IA peut citer des sources et tout de même utiliser les mauvais éléments de preuve. Cet article présente une méthode pratique pour vérifier le soutien des affirmations, l'autorité de la source, l'applicabilité, la provenance et si les éléments de preuve ont réellement influencé la réponse.","\u002Fuploads\u002F2026\u002F09\u002Fhow-to-know-whether-an-ai-agent-actually-used-the-right-evidence-1790351317188-o5z9ve.webp","2026-09-25T11:47:00.000Z",{"id":854,"slug":855,"title":856,"excerpt":857,"featuredImage":858,"publishedAt":859},"479","where-does-an-llm-get-its-data-rag-data-sources-in-python","D'où un LLM tire-t-il ses données ? Sources de données RAG en Python","Un LLM ne connaît pas magiquement vos fichiers, bases de données ou API. Cette suite pratique de la série sur le RAG montre, avec du Python simple, comment des données externes deviennent des preuves récupérables : des fichiers texte et du SQL à la recherche en texte intégral, aux embeddings, à l'assemblage du contexte et à l'appel final au LLM.","\u002Fuploads\u002F2026\u002F09\u002Fwhere-does-an-llm-get-its-data-rag-data-sources-in-python-1790517200521-nfsi5i.webp","2026-09-27T05:51:00.000Z",{"id":861,"slug":862,"title":863,"excerpt":864,"featuredImage":865,"publishedAt":866},"384","new-qwen-3-5-plus","Nouveau Qwen 3.5-Plus : l'IA open-source passe aux choses sérieuses","Découvrez les fonctionnalités et avantages révolutionnaires de Qwen 3.5-Plus d'Alibaba, une IA open-source qui change la donne pour les développeurs.","\u002Fuploads\u002F2026\u002F02\u002Fnew-qwen-3-5-plus-1771515512741-dcbi9p.webp","2026-02-19T10:23:00.000Z",{"id":868,"slug":869,"title":870,"excerpt":871,"featuredImage":872,"publishedAt":873},"484","what-is-an-ai-platform-architect-models-data-runtime-security-and-operations","Qu'est-ce qu'un architecte de plateforme d'IA ? Modèles, données, environnement d'exécution, sécurité et opérations","Un architecte de plateforme d'IA conçoit des fondations d'IA réutilisables à travers les modèles, les fournisseurs, la récupération, les agents, l'identité, la sécurité, l'évaluation, l'observabilité et les opérations.","\u002Fuploads\u002F2026\u002F10\u002Fwhat-is-an-ai-platform-architect-models-data-runtime-security-and-operations-1791477229171-ou3zcc.webp","2026-10-08T12:32:00.000Z",{"id":875,"slug":876,"title":877,"excerpt":878,"featuredImage":879,"publishedAt":880},"9","ubuntu-graphics-stack-transition-hybrid-gpu-boot-crashes-wayland-risks-and-stable-deployment-practices","Transition de la pile graphique Ubuntu : Plantages au démarrage avec GPU hybride, risques liés à Wayland et pratiques de déploiement stable","Les mises à niveau du bureau Ubuntu peuvent déclencher des blocages au démarrage, des sessions de connexion manquantes et un rendu instable—surtout sur les systèmes hybrides Intel + NVIDIA. Cet article explique la transition sous-jacente de la pile graphique, pourquoi les régressions se produisent et comment déployer Ubuntu en toute sécurité en utilisant les bases LTS et des stratégies de pilotes validées.","\u002Fuploads\u002F2026\u002F01\u002Fchatgpt-image-jan-17-2026-05-23-25-pm-1768673754531-r4c498.webp","2026-01-18T19:14:00.000Z",{"id":882,"slug":883,"title":884,"excerpt":885,"featuredImage":886,"publishedAt":887},"487","vector-databases-embeddings-and-reranking-three-different-parts-of-retrieval","Bases de données vectorielles, plongements et reclassement : trois parties distinctes de la recherche","Les embeddings représentent le sens, les bases de données vectorielles récupèrent des candidats, et les rerankers affinent les résultats. Découvrez comment ces trois couches de récupération diffèrent et fonctionnent ensemble dans le RAG.","\u002Fuploads\u002F2026\u002F10\u002Fvector-databases-embeddings-and-reranking-three-different-parts-of-retrieval-1791480129884-9dtasz.webp","2026-10-08T11:21:00.000Z",{"id":889,"slug":890,"title":891,"excerpt":892,"featuredImage":893,"publishedAt":894},"469","rag-failed-but-which-layer-actually-failed-a-diagnostic-method","Échec du RAG — mais quelle couche a réellement échoué ? Une méthode de diagnostic","Lorsqu'une réponse RAG est erronée, blâmer la récupération ou le modèle est trop vague. Cette méthode de diagnostic isole la couverture des sources, la construction de la requête, la récupération, le classement, l'assemblage du contexte, la génération, l'attribution des preuves et la fraîcheur—afin que la défaillance réelle puisse être reproduite et corrigée.","\u002Fuploads\u002F2026\u002F09\u002Frag-failed-but-which-layer-actually-failed-a-diagnostic-method-1790350847177-pior4c.webp","2026-09-24T19:39:00.000Z",{"id":896,"slug":897,"title":898,"excerpt":899,"featuredImage":900,"publishedAt":901},"495","sovereign-ai-control-of-models-data-infrastructure-and-dependencies","IA souveraine : contrôle des modèles, des données, des infrastructures et des dépendances","L'IA souveraine concerne le contrôle effectif sur les modèles, les données, l'infrastructure, les logiciels, les opérations et les dépendances stratégiques — et non simplement l'endroit où un modèle d'IA est hébergé.","\u002Fuploads\u002F2026\u002F10\u002Fsovereign-ai-control-of-models-data-infrastructure-and-dependencies-1791488833132-niy85x.webp","2026-10-08T15:45:00.000Z","fallback",[],[]]