{"id":6715,"date":"2022-06-30T10:46:08","date_gmt":"2022-06-30T10:46:08","guid":{"rendered":"https:\/\/digicomcorporation.com\/?p=6715"},"modified":"2022-07-13T08:39:01","modified_gmt":"2022-07-13T08:39:01","slug":"deployer-servicenow-les-10-erreurs-a-eviter","status":"publish","type":"post","link":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/","title":{"rendered":"D\u00e9ployer ServiceNow : les 10 erreurs \u00e0 \u00e9viter"},"content":{"rendered":"<h2><span style=\"font-weight: 400; font-size: 28px;\">1. Ignorer l\u2019\u00e9cart avec les bonnes pratiques ITIL.<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cMesurer l\u2019organisation\u201d<\/span><\/i><\/p>\n<p><b>Si vous ne connaissez pas l\u2019\u00e9cart de votre organisation avec les bonnes pratiques, il sera tr\u00e8s difficile voire impossible d\u2019avancer sereinement et accro\u00eetre les niveaux des services.<\/b><\/p>\n<p><b>La mise en place de nouveaux processus sera tr\u00e8s complexe.\u00a0<\/b><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; Faire un audit de maturit\u00e9 ITIL afin d\u2019\u00e9tablir ce qui fonctionne d\u00e9j\u00e0 correctement et se fixer les axes d\u2019\u00e9volution.<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">2. Consid\u00e9rer la formation et la certification ITIL comme optionnelle.<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cFormation et certification ITIL\u201d<\/span><\/i><\/p>\n<p><b>Ne pas conna\u00eetre les bonnes pratiques ainsi que ne pas certifier certains collaborateurs provoquera des incompr\u00e9hensions et des incoh\u00e9rences sur l\u2019ensemble des \u00e9l\u00e9ments mis en place. Il ne sera alors pas possible de r\u00e9pondre aux exigences du business avec des services fiables et optimis\u00e9s<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; Former les \u00e9quipes aux bonnes pratiques ITIL, respecter 4 dimensions de la gestion des services ainsi que les <a href=\"https:\/\/digicomcorporation.com\/fr\/actualites\/itil\/les-7-principes-directeurs-ditil-v4\/\">7 principes directeurs d&#8217;ITIL V4<\/a>. Certifier l\u2019ensemble des acteurs cl\u00e9 (administrateur ServiceNow, gestionnaires et propri\u00e9taires de processus).<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">3. Pensez que Servicenow permet de s&#8217;affranchir de la mise en place de processus<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cProcessus de gestion\u201d<\/span><\/i><\/p>\n<p><b>Des processus inexistants ou peu document\u00e9s entra\u00eenent un travail complexe entre les acteurs et se traduisent par un risque d\u2019augmentation des co\u00fbts de fonctionnement.<\/b><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; Mettre en place une d\u00e9marche processus de gestion des services (incidents, catalogue de service, probl\u00e8mes, changements, base de connaissance ainsi que la CMDB).<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">4. Vouloir tout int\u00e9grer trop rapidement<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cAvancer pas \u00e0 pas\u201d<\/span><\/i><\/p>\n<p><b>\u00c9viter de consid\u00e9rer le d\u00e9ploiement comme une action \u00ab One Shot \u00bb. Par exemple, d\u00e9ployer un portail client (front-office) avant d\u2019avoir pleinement int\u00e9grer et optimiser les process IT en back-office fragilisera fortement les processus en place<\/b><span style=\"font-weight: 400;\">. <\/span><b>Cela introduira une augmentation des sollicitations des \u00e9quipes qui se traduira par des d\u00e9lais et des co\u00fbts en augmentation<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; D\u00e9ployer les processus et les services pas \u00e0 pas les uns apr\u00e8s les autres. Se concentrer sur le d\u00e9ploiement des processus IT (back-office) en priorisant ceux qui fonctionnent d\u00e9j\u00e0 bien, puis d\u00e9ployer la partie portail utilisateurs (front-office).<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">5. Se passer d\u2019un administrateur Servicenow<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cUn administrateur de la plateforme\u201d<\/span><\/i><\/p>\n<p><b>Sans administrateur toute \u00e9volution ou modification impactera le co\u00fbt de maintenance de la solution et va fortement ralentir la mise en place d\u2019\u00e9volutions ou l\u2019ajout de nouveaux services.<\/b><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; Former une ressource pour administrer ServiceNow (conna\u00eetre les technologies WEB\/Javascript\/Ajax, html\/CSS, profil d\u00e9veloppeur\/ing\u00e9nieur). Cette ressource sera le pilier des \u00e9volutions de l\u2019instance et assurera la coh\u00e9rence des services, l\u2019ajout de nouveaux services ainsi que le processus d\u2019am\u00e9lioration continue.<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">6. Minimiser l\u2019importance de la communication et de la conduite du changement<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cConduite du changement\u201d<\/span><\/i><\/p>\n<p><b>\u00c9viter les points de blocage et les incompr\u00e9hensions, qui conduisent \u00e0 l&#8217;\u00e9chec.<\/b><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; S\u2019assurer une communication constante autour du projet, afin de s\u2019assurer la constante adh\u00e9sion des \u00e9quipes. Bien d\u00e9finir l\u2019objectif avec les parties prenantes et adopter des m\u00e9thodes de gestion de projet comme Agile pour avancer progressivement.<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">7. Rester ancr\u00e9e dans ses habitudes<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cAdopter une vision holistique et pragmatique.\u201d<\/span><\/i><\/p>\n<p><b>S\u2019attacher \u00e0 fonctionner \u00ab comme avant \u00bb conduira \u00e0 sortir tr\u00e8s souvent du standard et s\u2019\u00e9carter d\u2019ITIL, cela implique un co\u00fbt important de maintenance et des traitements qui risquent de ne pas \u00eatre optimis\u00e9s.<\/b><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; Ne pas vouloir continuer \u00e0 fonctionner \u00ab comme avant \u00bb (outil pr\u00e9c\u00e9dent et\/ou habitudes de fonctionnement des \u00e9quipes). Privil\u00e9gier d\u2019utiliser les fonctionnalit\u00e9s standard en accord avec les bonnes pratiques ITIL. Passer par des ateliers pour chaque processus en int\u00e9grant l\u2019ensemble parties prenantes (hotliners, techniciens, exploitation, gestionnaire de parc, projets, management, utilisateurs, etc\u2026.).<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">8. Fonctionner en vase clos\u00a0<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cTransversalit\u00e9 et management.\u201d<\/span><\/i><\/p>\n<p><b>Le manque de liens entre les \u00e9quipes ainsi que ne pas tenir compte des retours utilisateurs, fragilisera la qualit\u00e9 des services rendus, ce qui entra\u00eenera une augmentation des sollicitations et des d\u00e9lais, donc une perte financi\u00e8re pour le Business.<\/b><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; Travailler de mani\u00e8re transversale et non en \u00ab silo \u00bb. Privil\u00e9gier et accompagner les \u00e9quipes autour d\u2019un fonctionnement inter-\u00e9quipes, ne pas travailler en mode \u00ab silo \u00bb.<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">9. Ignorer le besoin de faire \u00e9voluer l\u2019outil de mani\u00e8re continue<\/span><\/h2>\n<p><i><span style=\"font-weight: 400;\">\u201cSe mesurer et s\u2019am\u00e9liorer\u201d<\/span><\/i><\/p>\n<p><b>Sans retours et mesures il ne sera pas possible de progresser et d\u2019int\u00e9grer de nouveaux services, ce qui conduira \u00e0 une obsolescence et un d\u00e9calage entre les besoins clients et les services mis \u00e0 disposition.<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Pour chaque processus (Incident, demandes, etc\u2026), d\u00e9finir des KPI (mesures), mettre en place les instances de gouvernance r\u00e9guli\u00e8res (utiliser les dashboard et le reporting afin de mesurer les indicateurs cl\u00e9 d\u00e9finis par l\u2019organisation). Ces retours serviront de base \u00e0 l\u2019am\u00e9lioration continue des services.<\/span><\/p>\n<h2><span style=\"font-weight: 400; font-size: 28px;\">10. Ne pas s\u2019engager sur des niveaux de service.<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">\u201cNiveaux de service\u201d<\/span><\/p>\n<p><b>Une mauvaise \u00e9valuation des niveaux de service (SLA) est un risque important d\u2019\u00e9chec sur la mise en place de la solution (risque de mettre toutes les parties prenantes sous tension avec un perte de qualit\u00e9 des services rendus).<\/b><\/p>\n<p><span style=\"font-weight: 400;\">-&gt; Viser \u00e0 d\u00e9finir des niveaux de service (SLA). Ce sont les indicateurs n\u00e9cessaires pour mesurer que les services sont d\u00e9livr\u00e9s comme attendu. Toutefois, ils ne peuvent \u00eatre d\u00e9finis qu&#8217;une fois que les processus bien \u00e9tablis et en place et que suffisamment de donn\u00e9es existent.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>1. Ignorer l\u2019\u00e9cart avec les bonnes pratiques ITIL. \u201cMesurer l\u2019organisation\u201d Si vous ne connaissez pas l\u2019\u00e9cart de votre organisation avec les bonnes pratiques, il sera tr\u00e8s difficile voire impossible d\u2019avancer sereinement et accro\u00eetre les niveaux des services. La mise en place de nouveaux processus sera tr\u00e8s complexe.\u00a0 -&gt; Faire un audit de maturit\u00e9 ITIL afin [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":6726,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[121],"tags":[],"post_flags":[],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>D\u00e9ployer ServiceNow : les 10 erreurs \u00e0 \u00e9viter | Digicom Corporation, IT Consulting &amp; ServiceNow Partner<\/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:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"D\u00e9ployer ServiceNow : les 10 erreurs \u00e0 \u00e9viter | Digicom Corporation, IT Consulting &amp; ServiceNow Partner\" \/>\n<meta property=\"og:description\" content=\"1. Ignorer l\u2019\u00e9cart avec les bonnes pratiques ITIL. \u201cMesurer l\u2019organisation\u201d Si vous ne connaissez pas l\u2019\u00e9cart de votre organisation avec les bonnes pratiques, il sera tr\u00e8s difficile voire impossible d\u2019avancer sereinement et accro\u00eetre les niveaux des services. La mise en place de nouveaux processus sera tr\u00e8s complexe.\u00a0 -&gt; Faire un audit de maturit\u00e9 ITIL afin [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/\" \/>\n<meta property=\"og:site_name\" content=\"Digicom Corporation, IT Consulting &amp; ServiceNow Partner\" \/>\n<meta property=\"article:published_time\" content=\"2022-06-30T10:46:08+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-07-13T08:39:01+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/digicomcorporation.com\/wp-content\/uploads\/2022\/06\/Frame-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1000\" \/>\n\t<meta property=\"og:image:height\" content=\"472\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"hello@digicomcorporation.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"hello@digicomcorporation.com\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"D\u00e9ployer ServiceNow : les 10 erreurs \u00e0 \u00e9viter | Digicom Corporation, IT Consulting &amp; ServiceNow Partner","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:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/","og_locale":"fr_FR","og_type":"article","og_title":"D\u00e9ployer ServiceNow : les 10 erreurs \u00e0 \u00e9viter | Digicom Corporation, IT Consulting &amp; ServiceNow Partner","og_description":"1. Ignorer l\u2019\u00e9cart avec les bonnes pratiques ITIL. \u201cMesurer l\u2019organisation\u201d Si vous ne connaissez pas l\u2019\u00e9cart de votre organisation avec les bonnes pratiques, il sera tr\u00e8s difficile voire impossible d\u2019avancer sereinement et accro\u00eetre les niveaux des services. La mise en place de nouveaux processus sera tr\u00e8s complexe.\u00a0 -&gt; Faire un audit de maturit\u00e9 ITIL afin [&hellip;]","og_url":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/","og_site_name":"Digicom Corporation, IT Consulting &amp; ServiceNow Partner","article_published_time":"2022-06-30T10:46:08+00:00","article_modified_time":"2022-07-13T08:39:01+00:00","og_image":[{"width":1000,"height":472,"url":"https:\/\/digicomcorporation.com\/wp-content\/uploads\/2022\/06\/Frame-1.png","type":"image\/png"}],"author":"hello@digicomcorporation.com","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"hello@digicomcorporation.com","Dur\u00e9e de lecture estim\u00e9e":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/#article","isPartOf":{"@id":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/"},"author":{"name":"hello@digicomcorporation.com","@id":"https:\/\/digicomcorporation.com\/fr\/#\/schema\/person\/5845420007ce658565d3c946a9513cad"},"headline":"D\u00e9ployer ServiceNow : les 10 erreurs \u00e0 \u00e9viter","datePublished":"2022-06-30T10:46:08+00:00","dateModified":"2022-07-13T08:39:01+00:00","mainEntityOfPage":{"@id":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/"},"wordCount":923,"publisher":{"@id":"https:\/\/digicomcorporation.com\/fr\/#organization"},"image":{"@id":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/#primaryimage"},"thumbnailUrl":"https:\/\/digicomcorporation.com\/wp-content\/uploads\/2022\/06\/Frame-1.png","articleSection":["ServiceNow\u00ae"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/","url":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/","name":"D\u00e9ployer ServiceNow : les 10 erreurs \u00e0 \u00e9viter | Digicom Corporation, IT Consulting &amp; ServiceNow Partner","isPartOf":{"@id":"https:\/\/digicomcorporation.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/#primaryimage"},"image":{"@id":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/#primaryimage"},"thumbnailUrl":"https:\/\/digicomcorporation.com\/wp-content\/uploads\/2022\/06\/Frame-1.png","datePublished":"2022-06-30T10:46:08+00:00","dateModified":"2022-07-13T08:39:01+00:00","inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/digicomcorporation.com\/fr\/actualites\/servicenow\/deployer-servicenow-les-10-erreurs-a-eviter\/#primaryimage","url":"https:\/\/digicomcorporation.com\/wp-content\/uploads\/2022\/06\/Frame-1.png","contentUrl":"https:\/\/digicomcorporation.com\/wp-content\/uploads\/2022\/06\/Frame-1.png","width":1000,"height":472},{"@type":"WebSite","@id":"https:\/\/digicomcorporation.com\/fr\/#website","url":"https:\/\/digicomcorporation.com\/fr\/","name":"Digicom Corporation, IT Consulting &amp; ServiceNow Partner","description":"Profitez du Consulting IT au meilleur rapport efficacit\u00e9 \/ prix sur les technologies Cloud ServiceNow, SAP et SalesForce.","publisher":{"@id":"https:\/\/digicomcorporation.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/digicomcorporation.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/digicomcorporation.com\/fr\/#organization","name":"Digicom Corporation","url":"https:\/\/digicomcorporation.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/digicomcorporation.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/digicomcorporation.com\/wp-content\/uploads\/2021\/08\/Logo-Digicom-Corporation-500.svg","contentUrl":"https:\/\/digicomcorporation.com\/wp-content\/uploads\/2021\/08\/Logo-Digicom-Corporation-500.svg","width":1,"height":1,"caption":"Digicom Corporation"},"image":{"@id":"https:\/\/digicomcorporation.com\/fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/digicom-corporation\/"]},{"@type":"Person","@id":"https:\/\/digicomcorporation.com\/fr\/#\/schema\/person\/5845420007ce658565d3c946a9513cad","name":"hello@digicomcorporation.com","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/digicomcorporation.com\/fr\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3d7fcce3efa14c124cc740cc56bea41c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3d7fcce3efa14c124cc740cc56bea41c?s=96&d=mm&r=g","caption":"hello@digicomcorporation.com"},"sameAs":["http:\/\/dcorp.coactis.fr"]}]}},"_links":{"self":[{"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/posts\/6715"}],"collection":[{"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/comments?post=6715"}],"version-history":[{"count":12,"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/posts\/6715\/revisions"}],"predecessor-version":[{"id":6799,"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/posts\/6715\/revisions\/6799"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/media\/6726"}],"wp:attachment":[{"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/media?parent=6715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/categories?post=6715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/tags?post=6715"},{"taxonomy":"post_flag","embeddable":true,"href":"https:\/\/digicomcorporation.com\/fr\/wp-json\/wp\/v2\/post_flags?post=6715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}