[{"data":1,"prerenderedAt":48},["ShallowReactive",2],{"articles":3,"site_settings":43},[4,19,31],{"id":5,"archived":6,"sort":7,"slug":8,"image":9,"fr_alt":7,"en_alt":7,"fr_tag":10,"en_tag":11,"date":12,"fr_title":13,"en_title":14,"fr_description":15,"en_description":16,"fr_body":17,"en_body":18},1,false,null,"structurer-cahier-des-charges-2024","20fc6714-7211-4c15-9875-c6dc48602115","Méthodologie","Methodology","2024-05-15T00:00:00","Structurer un cahier des charges solide en 2024","Structuring a solid project specification in 2024","Les 7 étapes incontournables pour rédiger un CDC qui protège le projet et facilite le delivery.","The 7 essential steps to write a spec document that protects the project and eases delivery.","\u003Cp>Un cahier des charges n'est pas un document administratif à cocher — c'est le socle qui protège le projet des dérives de périmètre et facilite le dialogue entre métier et équipes techniques.\u003C\u002Fp>\u003Cp>Les 7 étapes clés : contexte et enjeux, objectifs mesurables, périmètre fonctionnel, contraintes techniques, critères d'acceptation, planning macro, et gouvernance projet.\u003C\u002Fp>\u003Cp>Un CDC bien structuré ne fige pas le projet : il donne un cadre clair à l'intérieur duquel l'équipe peut avancer avec agilité, sans perdre de vue les objectifs business.\u003C\u002Fp>","\u003Cp>A project specification isn't an administrative box to tick — it's the foundation that protects the project from scope drift and eases dialogue between business and technical teams.\u003C\u002Fp>\u003Cp>The 7 key steps: context and stakes, measurable objectives, functional scope, technical constraints, acceptance criteria, high-level schedule, and project governance.\u003C\u002Fp>\u003Cp>A well-structured spec doesn't freeze the project: it gives the team a clear frame within which to move with agility, without losing sight of business goals.\u003C\u002Fp>",{"id":20,"archived":6,"sort":7,"slug":21,"image":22,"fr_alt":7,"en_alt":7,"fr_tag":23,"en_tag":23,"date":24,"fr_title":25,"en_title":26,"fr_description":27,"en_description":28,"fr_body":29,"en_body":30},2,"nuxt3-directus-portfolio-pm-tech","ff52612a-664d-4f1b-8998-7f81c4190c6b","Tech","2024-04-03T00:00:00","Nuxt 3 + Directus : le duo parfait pour un portfolio PM tech","Nuxt 3 + Directus: the perfect duo for a tech PM portfolio","Retour d'expérience sur l'architecture choisie pour ce portfolio — simplicité, performance et autonomie.","A behind-the-scenes look at the architecture chosen for this portfolio — simplicity, performance, and autonomy.","\u003Cp>Pour ce portfolio, j'ai choisi une architecture découplée : un frontend Nuxt en génération statique (SSG) et un CMS headless Directus self-hosted pour la gestion de contenu.\u003C\u002Fp>\u003Cp>Cette approche offre le meilleur des deux mondes : des performances de site statique (Lighthouse proche de 100) et une autonomie totale pour mettre à jour projets, articles ou CV sans toucher au code.\u003C\u002Fp>\u003Cp>Un webhook Directus déclenche un rebuild automatique du site à chaque modification de contenu — aucune intervention technique n'est nécessaire au quotidien.\u003C\u002Fp>","\u003Cp>For this portfolio, I chose a decoupled architecture: a statically generated (SSG) Nuxt frontend and a self-hosted Directus headless CMS for content management.\u003C\u002Fp>\u003Cp>This approach offers the best of both worlds: static-site performance (near-100 Lighthouse scores) and full autonomy to update projects, articles, or resume without touching the code.\u003C\u002Fp>\u003Cp>A Directus webhook triggers an automatic site rebuild on every content change — no technical intervention needed day to day.\u003C\u002Fp>",{"id":32,"archived":6,"sort":7,"slug":33,"image":34,"fr_alt":7,"en_alt":7,"fr_tag":35,"en_tag":35,"date":36,"fr_title":37,"en_title":38,"fr_description":39,"en_description":40,"fr_body":41,"en_body":42},3,"agile-vs-waterfall","ede3f3a4-b392-4bab-b31a-d1519a45b9a6","Agile","2024-02-18T00:00:00","Agile vs Waterfall : choisir selon le contexte projet","Agile vs Waterfall: choosing based on project context","La vraie question n'est pas quelle méthode est \"meilleure\" — c'est quelle méthode correspond à votre contexte.","The real question isn't which method is \"better\" — it's which method fits your context.","\u003Cp>Agile et Waterfall sont souvent opposés comme s'il fallait choisir un camp. En réalité, chaque méthode répond à des contextes projet différents.\u003C\u002Fp>\u003Cp>Waterfall reste pertinent quand les exigences sont stables et connues à l'avance (réglementaire, infrastructure critique). Agile excelle quand l'incertitude est forte et que l'itération rapide crée de la valeur.\u003C\u002Fp>\u003Cp>Le rôle du PM est de diagnostiquer le contexte — stabilité des exigences, criticité, culture d'équipe — avant de choisir le cadre méthodologique, plutôt que d'appliquer un dogme par défaut.\u003C\u002Fp>","\u003Cp>Agile and Waterfall are often pitted against each other as if you had to pick a side. In reality, each method answers different project contexts.\u003C\u002Fp>\u003Cp>Waterfall remains relevant when requirements are stable and known upfront (regulatory, critical infrastructure). Agile excels when uncertainty is high and fast iteration creates value.\u003C\u002Fp>\u003Cp>The PM's role is to diagnose the context — requirement stability, criticality, team culture — before choosing the methodological framework, rather than applying a default dogma.\u003C\u002Fp>",{"id":5,"logo_text":44,"fr_tagline":45,"en_tagline":45,"fr_copyright":46,"en_copyright":47},"WT","Project Manager IT + Tech · Douala, Cameroun","William TOKAM · Tous droits réservés","William TOKAM · All rights reserved",1785099906641]