In theory, yes. However, it becomes a bit more complex when the product being developed is a back-end system or service provided to other systems within the architecture. The standard “As a…” format is a great way to get people thinking about business value and actors/actions; the who, what, and why of the Story. The how should emerge via tasks during the sprint.
This was a nicely done visual representation of the simplicity of user stories, though. Thanks for sharing!
In theory, yes. However, it becomes a bit more complex when the product being developed is a back-end system or service provided to other systems within the architecture. The standard “As a…” format is a great way to get people thinking about business value and actors/actions; the who, what, and why of the Story. The how should emerge via tasks during the sprint.
This was a nicely done visual representation of the simplicity of user stories, though. Thanks for sharing!
Hi Daniel,
Do you feel that its still useful to use this format when working on a more back end system ?
Have you created something more effective ?
Be great to get your thoughts…
cheers
Cuan