GitScrum User Stories
User stories should be clear and use a non-technical language
The idea is that, after reading a user story, the team will understand the purpose of their work and what value is created by each activity performed.
Never pay monthly again for a Project Management Tool
User Story in organizing your Team’s Work
A user story usually follows this structure:
As a [persona] I want to [do something/get something] so then I can [get something/accomplish something]