{"id":3555,"date":"2013-03-21T14:38:38","date_gmt":"2013-03-21T13:38:38","guid":{"rendered":"http:\/\/www.solucominsight.fr\/?p=3555"},"modified":"2015-01-21T09:54:25","modified_gmt":"2015-01-21T08:54:25","slug":"le-passage-du-build-au-run-un-sujet-trop-souvent-neglige","status":"publish","type":"post","link":"https:\/\/www.riskinsight-wavestone.com\/en\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/","title":{"rendered":"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ?"},"content":{"rendered":"<p><em>Au lancement d\u2019un projet informatique, bien que les co\u00fbts de maintenance et d\u2019exploitation d\u2019une application soient en moyenne 4 \u00e0 5 fois sup\u00e9rieurs \u00e0 ceux de conception et de mise en oeuvre, les exigences et contraintes du run ne sont que tr\u00e8s rarement prises en compte. Pourtant, d\u00e8s son d\u00e9marrage, le projet ne devrait pas se focaliser uniquement sur sa cible initiale mais bien s\u2019attacher \u00e0 rechercher le bon compromis entre les objectifs du build et les contraintes du run. Quelles cons\u00e9quences sur l\u2019organisation des \u00e9quipes, notamment en charge du run ? Quels impacts sur le service d\u00e9livr\u00e9 et sur l\u2019efficacit\u00e9 des processus de run\u00a0? Toutes les comp\u00e9tences requises \u00e0 l\u2019exploitation du futur syst\u00e8me sont-elles disponibles\u00a0? <\/em><\/p>\n<h2>Diff\u00e9rentes contraintes \u00e0 prendre en compte pour assurer le succ\u00e8s d\u2019un projet<strong> <\/strong><\/h2>\n<p>Tout au long de la vie du projet, la prise en compte des contraintes du <em>run<\/em> doit tendre \u00e0 s\u2019affiner au fur et \u00e0 mesure que se pr\u00e9cise la vision de la cible attendue. De cette analyse doit alors d\u00e9couler un plan d\u2019actions permettant d\u2019anticiper la future arriv\u00e9e en production du projet et d\u2019y pr\u00e9parer les \u00e9quipes de <em>run<\/em>.<\/p>\n<p>Cette attention est d\u00e9terminante dans le succ\u00e8s d\u2019un projet informatique et surtout dans la p\u00e9rennit\u00e9 de son exploitation car c\u2019est un pr\u00e9requis indispensable :<\/p>\n<ul>\n<li>Dans l\u2019identification des sujets centraux du transfert de connaissance vers les \u00e9quipes de <em>run\u00a0;<\/em><\/li>\n<li>A l\u2019acquisition de toutes les comp\u00e9tences requises pour la bonne exploitation du futur syst\u00e8me par ces m\u00eames \u00e9quipes\u00a0;<\/li>\n<li>A la d\u00e9finition de modalit\u00e9s de \u00ab\u00a0service management\u00a0\u00bb claires et partag\u00e9es.<\/li>\n<\/ul>\n<h2>Impliquer les \u00e9quipes de <em>run<\/em>\u00a0: cl\u00e9 de r\u00e9ussite du passage du <em>build<\/em> au <em>run<\/em><\/h2>\n<p>Bien s\u00fbr, le passage du <em>build<\/em> au <em>run<\/em> se pr\u00e9pare \u00e0 travers une bonne documentation du projet \u2013 et de pr\u00e9f\u00e9rence une documentation valid\u00e9e par les \u00e9quipes d\u2019exploitation \u2013, par la d\u00e9finition et\/ou la contractualisation de services aupr\u00e8s de l\u2019exploitant, par l\u2019impl\u00e9mentation d\u2019une matrice de r\u00f4les et responsabilit\u00e9s claire et compl\u00e8te et enfin par la mise en \u0153uvre progressive de processus de gestion des incidents, des demandes et des changements.<\/p>\n<p>Cependant, le v\u00e9ritable succ\u00e8s de ce transfert des \u00e9quipes de <em>build<\/em> vers les \u00e9quipes de <em>run<\/em> r\u00e9side aussi \u2013 et surtout\u00a0\u2013 dans l\u2019implication des \u00e9quipes de <em>run<\/em> d\u00e8s la phase de <em>design<\/em> du projet afin d\u2019influer sur l\u2019architecture du syst\u00e8me, d\u2019am\u00e9liorer le co\u00fbt de son cycle de vie et de pr\u00e9venir les risques li\u00e9s \u00e0 son exploitation.<\/p>\n<p>Mais comment impliquer les interlocuteurs du <em>run<\/em> dans le projet\u00a0? Sachant que les \u00e9quipes de <em>build<\/em> et celles de <em>run<\/em> sont g\u00e9n\u00e9ralement issues de direction diff\u00e9rentes. Qui est suppos\u00e9 diriger qui\u00a0? Qui est force de d\u00e9cision sur le projet\u00a0? \u00c0 quel moment se fait la bascule du pouvoir de d\u00e9cision\u00a0?<\/p>\n<h2>Quelques bonnes pratiques de DSI pour mobiliser les \u00e9quipes de <em>run<\/em><\/h2>\n<p>Autrefois, la r\u00e9ponse d\u2019une DSI \u00e0 l\u2019implication du <em>run<\/em> dans le projet passait par la d\u00e9signation d\u2019un ou plusieurs interlocuteurs privil\u00e9gi\u00e9s au sein de ces \u00e9quipes de <em>run<\/em>. Ces \u00ab\u00a0r\u00e9f\u00e9rents\u00a0\u00bb avaient en charge d\u2019assurer la coordination avec les \u00e9quipes de <em>build<\/em> et d\u2019acqu\u00e9rir dans le m\u00eame temps toute la connaissance projet. Mais tr\u00e8s vite, ces collaborateurs devenaient des points de contention, leur implication cr\u00e9ant un probl\u00e8me de gouvernance r\u00e9current\u00a0: qui les pilote\u00a0?<\/p>\n<p>Aujourd\u2019hui, d\u2019autres r\u00e9ponses \u00e9mergent. Parmi les plus judicieuses, r\u00e9sident notamment :<\/p>\n<ul>\n<li><strong>La cr\u00e9ation d\u2019\u00e9quipes projet \u00ab\u00a0mixtes\u00a0\u00bb<\/strong>, compos\u00e9es autant de personnes venues du <em>build<\/em> que de personnes venues du <em>run<\/em>\u00a0 et d\u00e9tach\u00e9es <strong>sous une direction unique<\/strong>\u00a0;<\/li>\n<li><strong>La cr\u00e9ation d\u2019instances de gouvernance autour de l\u2019architecture<\/strong> impliquant \u00e0 la fois les responsables de <em>run<\/em> et du <em>build<\/em> pour assurer la prise en compte des contraintes d\u2019exploitation d\u00e8s la phase de <em>design<\/em> du syst\u00e8me\u00a0;<\/li>\n<li><strong>La r\u00e9alisation de Proof of concept<\/strong> (POC) <strong>pour \u00e9prouver les modalit\u00e9s de <em>service management<\/em>\u00a0: <\/strong>l\u2019ensemble de mon processus est-il clairement ma\u00eetris\u00e9 et connu de tous ? Les diff\u00e9rentes parties prenantes sont-elles bien d\u00e9finies et en capacit\u00e9 de r\u00e9aliser leurs actions ?. Ce POC permet \u00e9galement de faciliter la mont\u00e9e en comp\u00e9tences des interlocuteurs de <em>run<\/em> sur la prise de d\u00e9cision\u00a0: quoi faire et dans quel cas\u00a0?<\/li>\n<li><strong>La mise en \u0153uvre de p\u00e9riodes probatoires<\/strong> \u00e0 l\u2019issue de la mise en production pendant lesquelles les \u00e9quipes de <em>run<\/em> prennent progressivement la responsabilit\u00e9 du syst\u00e8me tout en conservant un support des \u00e9quipes de <em>build\u00a0;<\/em><\/li>\n<li><strong>La mise \u00e0 disposition de socles normalis\u00e9s port\u00e9s par des offres de services standardis\u00e9es<\/strong> permettant d\u2019inverser le probl\u00e8me\u00a0: il n\u2019appartient plus au <em>run<\/em> de r\u00e9pondre aux exigences du <em>build<\/em>. Au contraire, il devient de la responsabilit\u00e9 du projet de s\u2019inscrire dans les standards d\u2019exploitation d\u00e9finis.<\/li>\n<\/ul>\n<p>Quelles que soient les approches adopt\u00e9es, celles-ci visent toutes le m\u00eame eldorado\u00a0: trouver le parfait \u00e9quilibre entre objectifs du <em>build<\/em> et contraintes du <em>run<\/em>\u2026 et ainsi assurer la r\u00e9ussite totale du projet\u00a0!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Au lancement d\u2019un projet informatique, bien que les co\u00fbts de maintenance et d\u2019exploitation d\u2019une application soient en moyenne 4 \u00e0 5 fois sup\u00e9rieurs \u00e0 ceux de conception et de mise en oeuvre, les exigences et contraintes du run ne sont&#8230;<\/p>\n","protected":false},"author":1269,"featured_media":3385,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"page-templates\/tmpl-one.php","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[35],"tags":[578,1049,105,1050,1047,1051,1048],"coauthors":[],"class_list":["post-3555","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-strategie-projets-it","tag-architecture","tag-build","tag-gouvernance","tag-poc","tag-projet-informatique","tag-proof-of-concept","tag-run"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ? - RiskInsight<\/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.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ? - RiskInsight\" \/>\n<meta property=\"og:description\" content=\"Au lancement d\u2019un projet informatique, bien que les co\u00fbts de maintenance et d\u2019exploitation d\u2019une application soient en moyenne 4 \u00e0 5 fois sup\u00e9rieurs \u00e0 ceux de conception et de mise en oeuvre, les exigences et contraintes du run ne sont...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/\" \/>\n<meta property=\"og:site_name\" content=\"RiskInsight\" \/>\n<meta property=\"article:published_time\" content=\"2013-03-21T13:38:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2015-01-21T08:54:25+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"907\" \/>\n\t<meta property=\"og:image:height\" content=\"529\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"zephSolucomBO\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"zephSolucomBO\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/\"},\"author\":{\"name\":\"zephSolucomBO\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#\/schema\/person\/61c2fe74fad6b31442e1706ccacf3421\"},\"headline\":\"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ?\",\"datePublished\":\"2013-03-21T13:38:38+00:00\",\"dateModified\":\"2015-01-21T08:54:25+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/\"},\"wordCount\":898,\"publisher\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg\",\"keywords\":[\"architecture\",\"build\",\"gouvernance\",\"POC\",\"projet informatique\",\"proof of concept\",\"run\"],\"articleSection\":[\"M\u00e9tiers - Strat\u00e9gie &amp; projets IT\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/\",\"url\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/\",\"name\":\"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ? - RiskInsight\",\"isPartOf\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg\",\"datePublished\":\"2013-03-21T13:38:38+00:00\",\"dateModified\":\"2015-01-21T08:54:25+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#primaryimage\",\"url\":\"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg\",\"contentUrl\":\"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg\",\"width\":907,\"height\":529},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.riskinsight-wavestone.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#website\",\"url\":\"https:\/\/www.riskinsight-wavestone.com\/en\/\",\"name\":\"RiskInsight\",\"description\":\"The cybersecurity &amp; digital trust blog by Wavestone&#039;s consultants\",\"publisher\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.riskinsight-wavestone.com\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#organization\",\"name\":\"Wavestone\",\"url\":\"https:\/\/www.riskinsight-wavestone.com\/en\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2021\/08\/Monogramme\u2013W\u2013NEGA-RGB-50x50-1.png\",\"contentUrl\":\"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2021\/08\/Monogramme\u2013W\u2013NEGA-RGB-50x50-1.png\",\"width\":50,\"height\":50,\"caption\":\"Wavestone\"},\"image\":{\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.riskinsight-wavestone.com\/en\/#\/schema\/person\/61c2fe74fad6b31442e1706ccacf3421\",\"name\":\"zephSolucomBO\",\"url\":\"https:\/\/www.riskinsight-wavestone.com\/en\/author\/zephsolucombo\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ? - RiskInsight","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.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/","og_locale":"en_US","og_type":"article","og_title":"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ? - RiskInsight","og_description":"Au lancement d\u2019un projet informatique, bien que les co\u00fbts de maintenance et d\u2019exploitation d\u2019une application soient en moyenne 4 \u00e0 5 fois sup\u00e9rieurs \u00e0 ceux de conception et de mise en oeuvre, les exigences et contraintes du run ne sont...","og_url":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/","og_site_name":"RiskInsight","article_published_time":"2013-03-21T13:38:38+00:00","article_modified_time":"2015-01-21T08:54:25+00:00","og_image":[{"width":907,"height":529,"url":"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg","type":"image\/jpeg"}],"author":"zephSolucomBO","twitter_misc":{"Written by":"zephSolucomBO","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#article","isPartOf":{"@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/"},"author":{"name":"zephSolucomBO","@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#\/schema\/person\/61c2fe74fad6b31442e1706ccacf3421"},"headline":"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ?","datePublished":"2013-03-21T13:38:38+00:00","dateModified":"2015-01-21T08:54:25+00:00","mainEntityOfPage":{"@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/"},"wordCount":898,"publisher":{"@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#organization"},"image":{"@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#primaryimage"},"thumbnailUrl":"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg","keywords":["architecture","build","gouvernance","POC","projet informatique","proof of concept","run"],"articleSection":["M\u00e9tiers - Strat\u00e9gie &amp; projets IT"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/","url":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/","name":"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ? - RiskInsight","isPartOf":{"@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#primaryimage"},"image":{"@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#primaryimage"},"thumbnailUrl":"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg","datePublished":"2013-03-21T13:38:38+00:00","dateModified":"2015-01-21T08:54:25+00:00","breadcrumb":{"@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#primaryimage","url":"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg","contentUrl":"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2013\/03\/Fotolia_43983645_ampoule.jpg","width":907,"height":529},{"@type":"BreadcrumbList","@id":"https:\/\/www.riskinsight-wavestone.com\/2013\/03\/le-passage-du-build-au-run-un-sujet-trop-souvent-neglige\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.riskinsight-wavestone.com\/en\/"},{"@type":"ListItem","position":2,"name":"Le passage du build au run : un sujet trop souvent n\u00e9glig\u00e9 ?"}]},{"@type":"WebSite","@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#website","url":"https:\/\/www.riskinsight-wavestone.com\/en\/","name":"RiskInsight","description":"The cybersecurity &amp; digital trust blog by Wavestone&#039;s consultants","publisher":{"@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.riskinsight-wavestone.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#organization","name":"Wavestone","url":"https:\/\/www.riskinsight-wavestone.com\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2021\/08\/Monogramme\u2013W\u2013NEGA-RGB-50x50-1.png","contentUrl":"https:\/\/www.riskinsight-wavestone.com\/wp-content\/uploads\/2021\/08\/Monogramme\u2013W\u2013NEGA-RGB-50x50-1.png","width":50,"height":50,"caption":"Wavestone"},"image":{"@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.riskinsight-wavestone.com\/en\/#\/schema\/person\/61c2fe74fad6b31442e1706ccacf3421","name":"zephSolucomBO","url":"https:\/\/www.riskinsight-wavestone.com\/en\/author\/zephsolucombo\/"}]}},"_links":{"self":[{"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/posts\/3555","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/users\/1269"}],"replies":[{"embeddable":true,"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/comments?post=3555"}],"version-history":[{"count":6,"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/posts\/3555\/revisions"}],"predecessor-version":[{"id":4568,"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/posts\/3555\/revisions\/4568"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/media\/3385"}],"wp:attachment":[{"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/media?parent=3555"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/categories?post=3555"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/tags?post=3555"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.riskinsight-wavestone.com\/en\/wp-json\/wp\/v2\/coauthors?post=3555"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}