Technos
En bref
Client-side PM/AMOA for territorial portal scoping: align stakeholders, arbitrate cross-team roadmap trade-offs and secure long-run Jira execution.
Contexte
Client-side PM (AMOA) on the LAAD portal around Lake Annecy: scoping with stakeholders, prioritising change and steering delivery in Jira - the public site remains PHP / Bootstrap for local tourism. Scope focused on priority journeys and content readability.
Mission
Align marketing, partners and engineering on a segmented portal (stay, eat, activities) without a blurry backlog or colliding releases.
Livraison
Structured backlog in Jira, documented trade-offs and releases better synced with destination business needs.
Align marketing, partners and engineering on a segmented portal (stay, eat, activities) without a blurry backlog or colliding releases.
Structured backlog in Jira, documented trade-offs and releases better synced with destination business needs.
A destination portal is never “just one website”: it is verticals, seasons and actors on different clocks. On the AMOA side, the job is to fold that reality into a clear Jira backlog - what protects the visitor (navigation, readable directories), what serves partners (spotlights, consistent listings), and what can wait for the next cycle.
À compléter — budget, délais, conformité ou capacité équipe.
À compléter — friction parcours, lisibilité, confiance.
À compléter — priorisation, dette technique, mesure.
Without AMOA, requests pile up from every direction: everyone pushes their section, functional debt grows and no one decides at the right level. We needed a shared language (scope, acceptance criteria) and a single source of truth - Jira - so marketing, editorial and engineering share one roadmap.
Scoping workshops on core journeys (accommodation, dining, activities), slicing work into shippable increments, transparent prioritisation and acceptance testing. The site’s multi-colour design is not decoration: it encodes business segments; AMOA makes sure each colour maps to a useful journey, not a one-off whim.
Fewer “urgent” items that were never qualified, more traceable decisions: the portal can evolve season after season without every campaign turning into a mini crisis.
Technical performance
100%
Current performance observed on this project scope: 100%.
Accessibility
96%
Accessibility level observed on this scope: 96%.
Technical quality
96%
Technical quality level observed on this scope: 96%.
Performance globale
SCORE /100
Excellent
Moyenne des indicateurs apres optimisation
Lac Annecy relies on segment-based governance that keeps roadmap decisions readable despite stakeholder diversity and seasonal demand shifts.
Stay, eat, activities
Each change is assessed against visitor-use value before prioritization.
Traceability and alignment
Documented decisions reduce reliance on oral arbitration and fragmented context.
Directory and listing reliability
Publishing follows a repeatable acceptance rhythm on high-traffic content surfaces.
Ce site utilise des outils de mesure d’audience (Google Analytics 4) et d’expérience utilisateur (Microsoft Clarity), uniquement avec votre accord explicite. Politique de confidentialité.
Aucun cookie publicitaire ni de suivi individuel n’est utilisé : uniquement des statistiques anonymisées pour comprendre les usages du site.
