B S T O R I E S ? • A new way to gather requirements • A twist on user stories • Refocusses on causality • Refocusses on motivation • Hey, we’re agile, right?
W I T H P E R S O N A S • Are they fully fleshed out? • So what if they are? • Meaningless data == Noise • Noise == Distraction • Narrows scope • Assumptions about role importance
T I N G W I T H A C L I E N T, I WA N T T O I M P R E S S T H E M W I T H A G R E AT E X P E R I E N C E S O T H AT W E C A N D O B U S I N E S S T O G E T H E R F O R A L O N G T I M E
G RY A N D D O N ’ T H AV E A L O T O F T I M E I WA N T A WAY T O F E E L F U L L W I T H M I N I M A L E F F O R T S O T H AT I C A N G E T B A C K T O W H AT I WA S D O I N G A S A P.
I E S A R E N ’ T • Replacing conversations with users • Substitute for other requirements gathering techniques • (HINT: same holds true for user stories, btw)