Writing User Stories for Back-end Systems.
My favorite definition for a user story is that it is a thin, vertical slice of functionality, describing a small increment in value to the user (or customer). A task, on the other hand is a step taken by the development team, required to fulfill the requirements of the user story.
Don’t write too many details and don’t write the stories too early. Write them when they are needed and sick to the template. Discuss and formulate the stories together with the team. Write user stories for 1-2 sprints ahead. This makes you plan an enough time frame. It is better to write small user stories than large. Divide and conquer.
Why technical user stories are bad. Technical user stories are bad because they defeat the fundamental purpose of a user story. Which is to describe the desired behaviour from a user point of view. And to ensure that the value (for some person) is captured. Nobody gets value from an API talking to a database through an object-relational mapper.
Agile teams sometimes struggle with the planning of pure technical tasks that have no direct value for the user of a system, but have to be done to deliver working software. Should you create user sto.
Here’s what a set of user stories could look like. Overall, user stories are a key part in creating a useful user-oriented application. As long as you have a very clear understanding of your users, you will be able to create a great set of user stories that outlines the goals a user has for your application.
Technical stories with demonstrable business value are rare, but can and should be prioritized with user stories. Ron Jeffries has continued his work on technical stories in a new article stating.
Practical Security Stories and Security Tasks for Agile Development Environments JULY 17, 2012. While user stories center around “use cases” that allow the user to complete a certain task,. detailed and technical in nature and therefore are.