Kit kebutuhan agile
Alur kebutuhan product owner: persona, journey, story map, epic dan story, prioritas, kriteria penerimaan BDD, dan keterlacakan.
10 templat dalam 4 langkah, sesuai urutan penggunaan. Buka templat mana pun di editor, isi, lalu ekspor ke PDF, DOCX, atau HTML.
Penemuan kebutuhan
User Persona Template
StandarResearch-based persona: evidence table with sample and recency rules, goals and jobs, behaviour, needs to implications, scenarios, anti-persona, decision log
NN/g persona practiceCustomer Journey Map Template
StandarEvidence-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)
Perancangan solusi
User Story Map Template (Jeff Patton)
StandarPersonas, backbone of activities, walking skeleton, stories in release slices, release goals, Given/When/Then criteria
Jeff Patton, User Story Mapping (2014); INVEST (Wake, 2003)Epic Template
StandarOutcome-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 practiceUser Story Template
RingkasUser 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/ThenRICE Prioritization Template
StandarRICE 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)
Spesifikasi
BDD Acceptance Criteria Template (Gherkin)
StandarFeature, stories, rules with examples, Gherkin feature file (Rule, Background, Scenario Outline, tags), trace to tests, checklist, anti-patterns
Cucumber Gherkin referenceFunctional Specification Document (FSD) Template
LengkapRoles and permissions matrix, per-feature flows, business rules, validation, messages, data fields, reports, notifications
Common practice; ISO/IEC/IEEE 29148:2018 quality characteristics
Verifikasi
Requirements Traceability Matrix (RTM) Template
StandarForward 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)Definition of Done Template (Scrum)
StandarOrganisational minimum, team DoD criteria with evidence and automation, release quality gates, optional Definition of Ready, not-done rule, change log
Scrum Guide 2020