In the traditional software development method, requirements are noted as a handful of documentations, specifications...
In Agile, they are User Story is requirement. User Story is:
As a <role>, I want <feature> so that <reason>
Epic: A very large user story that will not fit into a single iteration, does not pass the test for inclusion in an iteration, and will need to be subdivided to be considered.
Theme: A collection of features, epics, & stories that describe a broad business purpose.
Sometimes the User Story will also include the design/wireframe for the screen and other extra information and will be logged as an item in the backlog (Like Trello card, Gitlab issue,...)
INVEST is an acronym which encompasses the following concepts which make up a good user story:
1. Start with personas
This is easily the most important step. Make sure to have a solid understanding of user personas in order to craft meaningful stories that actually speak to their needs, goals and frustrations. The personas is the foundation for the rest of the steps in this process, so make sure its compelling and accurate.
2. Take the personas goals and convert them into epics
What goals does the user want to accomplish? Assess these goals and convert them into broad epics. Epics are broad, and define context. The goals of the persona will help determine what functionality our product should include, and epics will give us a big picture idea of what features will look like.
3. Distill persona into roles & epics into stories
Based on who the user is and what’s they’re trying to accomplish, what different roles do they assume?
Then, select an epic and break it down into a more granular form.
The story is generally “done” when the user can complete the outlined task, but make sure to define what that is.
Drop us a message if you need any helps from the DwarvesLet's build