TLDR
The purpose of a user story is to describe the desired functionality of a specific part of the software. This description should inform the reader about the type of the user, expected outcome or problem that needs to be solved. The description should provide enough information for everyone to understand what is the task all about, but should avoid describing the solution. The classic format that almost every product owner uses is "As I […], I want to […, so that I can […]". This is the one that is commonly used because it answers a lot of questions.via the TL;DR App
no story
Written by dakic | Product Owner at Symphony.is |
https://www.narrativeplus.net | Author of Treasure Roadmap book.
