docs(daily-email): add 2022-12-04
This commit is contained in:
parent
6182b0efd6
commit
fe8810f6b4
25
website/src/daily-emails/2022-12-04.md
Normal file
25
website/src/daily-emails/2022-12-04.md
Normal file
|
@ -0,0 +1,25 @@
|
||||||
|
---
|
||||||
|
title: >
|
||||||
|
Writing "Why first" user stories
|
||||||
|
pubDate: 2022-12-04
|
||||||
|
permalink: >
|
||||||
|
archive/2022/12/04/writing-why-first-user-stories
|
||||||
|
---
|
||||||
|
|
||||||
|
I've usually written user stories that follow this format:
|
||||||
|
|
||||||
|
As a...
|
||||||
|
I want...
|
||||||
|
So that...
|
||||||
|
|
||||||
|
You focus on the person who needs the task first, followed by what they want, and why they want it.
|
||||||
|
|
||||||
|
Lately, I've been re-ordering stories to follow this order:
|
||||||
|
|
||||||
|
So that...
|
||||||
|
As a...
|
||||||
|
I want...
|
||||||
|
|
||||||
|
What I like about this is that it focuses on capturing the "why" of the story first rather than at the end or maybe even forgetting it altogether.
|
||||||
|
|
||||||
|
What's needed and who needs it doesn't matter unless you also capture why it's needed.
|
Loading…
Reference in a new issue