It’s all in how you say it. Or, in the case of this video, how you write it. In less than 2 minutes, this video will send a powerful message. It’s about writing from perspective.
After watching it, I immediately thought of how a user story can communicate a message differently, compared to a standard “shall statement” requirement.
Here are as few formats for you to compare. Which would you use?
As a <role>, I want <goal>
As a <role>, I want <goal> so <reason>
Given <dependency/constraint>, as a <role>, I want <goal> so <reason>
Do you have a preferred user story format that you use? Please include it as a comment and have a beautiful day.
Related posts:
- Using Stories on my Personal Kanban
- See Dick See Dick the PM Run
- Triple Constraint
- My Merge of GTD and Kanban
- Assumptions and Constraints