This article looks to discuss the ‘User Story Syntax’. It provides an introduction to the Agile User Story and discusses how they should be written.
An Introduction into Agile User Stories
A 59 Seconds Agile Training Video
Continue to Part 4 Below
User Story Syntax: How Should User Stories be Written?
A 59 Seconds Agile Article
This article provides an ‘Introduction to Agile’ and looks to discuss what Agile is. It provides a brief introduction into the history of Agile and why Agile is important.
User Story Syntax
Traditional projects would write requirements by listing what the system, feature, or component should do. For example, requirements for a Login Page would look like:
One, the system should have a login page that accepts a user’s email and password.
Two, the system should prompt the user with an error message when incorrect login credentials are entered.
Three, the system should have an option for login that lets the user access different applications with a single set of login credentials
When it comes to user stories, they would be written to include the user persona, their need, and their purpose for the functionality. The format for user stories is the following statement below:
As a user, I want to do an action, so that this benefit happens.
Taking the login requirement discussed earlier, its user story could look like:
As a user, I want to use a single set of login credentials so that I don’t have to repeatedly enter my email and password for every application in the suite.
Comparing it to its traditional requirement format, this user story shows in a single sentence what the user wants, why they want it, and what problem would be solved when the feature is done.
Continue Reading —> Next
The History of Agile
A 59 Seconds Agile Video Animation
Continue Reading —> Next
User Stories Applied
A 59 Seconds Agile Book Review
User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.
Continue Reading —> Next
What is Agile?
A 59 Seconds Agile Infographic
Continue Reading —> Next
Agile Scrum Master Training Course
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum:
Continue Reading —> Next
