Markdown Editor
Ouvrir l'éditeur

Kit exigences agiles

Flux d'exigences du product owner : personas, parcours, story map, epics et stories, priorisation, critères d'acceptation BDD et traçabilité.

10 modèles en 4 étapes, dans l'ordre d'utilisation. Ouvrez un modèle dans l'éditeur, complétez-le et exportez-le en PDF, DOCX ou HTML.

Étape 1

Découverte

  1. User Persona Template

    Standard

    Research-based persona: evidence table with sample and recency rules, goals and jobs, behaviour, needs to implications, scenarios, anti-persona, decision log

    NN/g persona practice

  2. Customer Journey Map Template

    Standard

    Evidence-based journey map: scope, evidence IDs per cell, stage grid, emotional curve, service blueprint layer, exits, moments of truth, metrics, fixes

    NN/g journey mapping; service blueprint (Shostack 1984)
Étape 2

Élaboration de la solution

  1. User Story Map Template (Jeff Patton)

    Standard

    Personas, backbone of activities, walking skeleton, stories in release slices, release goals, Given/When/Then criteria

    Jeff Patton, User Story Mapping (2014); INVEST (Wake, 2003)

  2. Epic Template

    Standard

    Outcome-shaped epic: hypothesis, scope, epic acceptance criteria, Definition of Done, story breakdown, dependencies, metrics, risks, release, closure

    Scrum Guide 2020 (Definition of Done); common agile practice

  3. User Story Template

    Léger

    User story with role, goal and benefit, Given/When/Then acceptance criteria, INVEST check, Definition of Done link, scope and UX notes

    INVEST (Wake, 2003); Gherkin Given/When/Then

  4. RICE Prioritization Template

    Standard

    RICE scoring (Effort in person-months), ranked commitment vs capacity, WSJF/ICE/Kano/MoSCoW cross-checks, not-doing list, dependencies, re-scoring

    RICE (Intercom, 2018); WSJF (SAFe); MoSCoW (DSDM); Kano (1984)
Étape 3

Spécifications

  1. BDD Acceptance Criteria Template (Gherkin)

    Standard

    Feature, stories, rules with examples, Gherkin feature file (Rule, Background, Scenario Outline, tags), trace to tests, checklist, anti-patterns

    Cucumber Gherkin reference

  2. Functional Specification Document (FSD) Template

    Complet

    Roles and permissions matrix, per-feature flows, business rules, validation, messages, data fields, reports, notifications

    Common practice; ISO/IEC/IEEE 29148:2018 quality characteristics
Étape 4

Vérification

  1. Requirements Traceability Matrix (RTM) Template

    Standard

    Forward and backward links from business need to tests and results, coverage metrics, orphan analysis, change impact

    ISO/IEC/IEEE 29148:2018 (Edition 3 at DIS stage)

  2. Definition of Done Template (Scrum)

    Standard

    Organisational minimum, team DoD criteria with evidence and automation, release quality gates, optional Definition of Ready, not-done rule, change log

    Scrum Guide 2020