Technos
En bref
Client-side PM/AMOA in Jira aligning marketing, academics and delivery teams, prioritizing roadmap value, and hardening acceptance quality.
Contexte
Client-side PM (AMOA) on the NOSCHOOL site: prioritisation with marketing and academic teams, scoping journeys (programmes, events, applications) and steering delivery in Jira - WordPress, PHP and Bootstrap stack. Scope focused on priority journeys and content readability.
Mission
Balance a very dense programme catalogue (tracks, levels, campuses, work-study vs initial), a packed events calendar and application conversion goals - without drowning teams or the technical roadmap.
Livraison
Requests structured in Jira, clearer priorities intake after intake and acceptance aligned with student and family journeys.
Balance a very dense programme catalogue (tracks, levels, campuses, work-study vs initial), a packed events calendar and application conversion goals - without drowning teams or the technical roadmap.
Requests structured in Jira, clearer priorities intake after intake and acceptance aligned with student and family journeys.
A business school website is a content and deadline factory: every intake adds campaigns, events and catalogue tweaks. AMOA acts as a filter - what deserves a product change, what is editorial-only, and what must be explicitly decided in Jira so nothing explodes as a hidden “urgent”.
À compléter — budget, délais, conformité ou capacité équipe.
À compléter — friction parcours, lisibilité, confiance.
À compléter — priorisation, dette technique, mesure.
Needs arrive in bursts - new track, new fair, new KPI block, application flow tweak. Without AMOA, engineering absorbs everything at the same level or marketing improvises as integrator. We needed a shared baseline: user stories, definition of done, visibility on what is committed for the sprint or the term.
Workshops with marketing and internal teams on critical journeys (orientation, events, application), batching work, prioritising in Jira and supporting acceptance. The yellow / black / white design system and full-radius CTAs stay the brand language; AMOA ties them to measurable goals, not just a graphic trend.
Intakes and event peaks become steerable: less scope creep, more traceability on what shipped and why.
Technical performance
98%
Current performance observed on this project scope: 98%.
Accessibility
100%
Accessibility level observed on this scope: 100%.
Technical quality
75%
Technical quality level observed on this scope: 75%.
Performance globale
SCORE /100
Excellent
Moyenne des indicateurs apres optimisation
NoSchool applies an AMOA operating model that turns scattered requests into value-driven backlog decisions and acceptance routines adapted to seasonal peak pressure.
Marketing, academics, delivery
Recurring workshops define one shared hierarchy before technical decomposition starts.
Objective-led epics
Backlog structure stays tied to business objectives to reduce unqualified urgency.
Pre-release discipline
Acceptance is designed for intake and event peaks, not only nominal traffic.
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.
