Contents
How granular should a user story be?
A user story should be written at a level of granularity that enables the development team to accurately estimate the level of effort it will take them to build functionality to support the story. When written too broadly, that is impossible.
Should user stories have technical details?
They must be written in the user’s usual business language and take the user’s point of view. At the same time, a single user story may include 30 or more specific technical requirements. User stories provide the basis for defining the system’s requirements and also facilitate the management of those requirements.
What makes a user story bad?
Stories Violate Any INVEST Quality Criteria Haven’t been discussed, questioned, or negotiated (or you skipped the conversation) Have no value to the customer or end users. Don’t have enough information to be sized or estimated by the team. Too big.
How to write user stories with multiple roles?
I have a number of user stories where the same feature needs to be shared by multiple roles. I have started writing these stories like this: Event-Y should occure. Is this the correct way to represent that concept in user stories, or should I break it up into one story for each role?
When to add more detail to user stories?
You may start by writing a story indicating nothing more than that: As a user, I can log in through a social media account. If the team won’t implement that story for a few iterations, this story is likely quite sufficient as is. However, as the time when the team will work this story approaches, additional detail is needed.
Which is better feature story or user story?
As Ba Luu and Maxim indicate these can be decomposed into User Stories. So features would be a higher level description of desired product aspects. The level of decomposition and the name you give it is not that important. Key is that you decompose the Product Backlog items to be small enough to be delivered in 1 increment. In 1 sprint.
What is the correct way to represent that concept in user stories?
Event-Y should occure. Is this the correct way to represent that concept in user stories, or should I break it up into one story for each role? [an example might help; there may be some role confusion taking place of roles A and B share a lot of the same stories; chances are there is a role C that ‘owns’ the common stories instead]