The following template describes the best development practices for writing Agile User Stories.
The user story should include the following:
- Title
- As a [user role], I want to [goal], so I can [reason].
- Build the screen shots with the screen specifications per feature. Identify the functionality and data requirements.
- Acceptance Criteria: Identify the test cases for both the success conditions and failure conditions for the user story.
Sample User Story:
AGILE USER STORIES FOR SEARCH PRODUCTS
US 1- As a customer, I want to search by product name, so I can see a list of products matching my search.
US 2- As a customer, I want to select a product, so I can view the product details.
Build the screen shots with the screen specifications per feature or list the functionality required for the feature. Identify the functionality and data requirements.
- On the product search page, display a Search field.
- Execute search and return list of matching products.
- On the product search page, click a product image or name to display the product details page.
Acceptance Criteria: (Identify the test cases for both the success conditions and failure conditions for the user story.}
Success:
- US1
- Search field is present
- Search can be executed
- Search can be edited
- Search can be cleared
- Search results be displayed
- Customer will be able to navigate to product details
- US2
- Display product image, name, availability and price
- Click a product image or name to view the product details page
Failure:
- US1
- Search field is disabled/not displayed
- Search button not enabled
- No matching search results (no data returned)
- Image/name doesn’t link to a product details page
- US2
- Product data not received
Find out more about the Agile method with the help of Pierson Requirements Groups’ blog on all things related to the businesses analysis training including helpful tip guides and company updates.
