Contents
What makes a user story independent?
Independent — To the maximum extent possible, one story should be independent of another. This is particularly important for stories that are being worked on during the same iteration (Sprint), since dependencies between stories during the same iteration complicate planning and prioritization.
What does it mean for a story to be independent?
1. In the context of INVEST, Independent is about being able to do the stories in any order rather than having to prioritize them by technical dependencies. It’s not about each story being unrelated to the others.
Can user stories be dependent?
A dependency between User Stories means that if US2 needs US1 then you must do US1 before US2. So Agile teams try to reduce the dependencies between User Stories to allow them to pull User Stories into development in any order the business wants.
What is meant by a user story being negotiable?
Negotiable: A story should be brief. It is not a detailed contract. It’s purpose is to encourage ongoing conversation and scope negotiation between the customer and the developers. Valuable: A story should provide value to the customer or the user.
What are three SAFe investment elements?
Bill Wake, coined the acronym INVEST [1], to describe the attributes of a good user story.
- I – Independent (among other stories)
- N – Negotiable (a flexible statement of intent, not a contract)
- V – Valuable (providing a valuable vertical slice to the customer)
- E – Estimable (small and negotiable)
How to write user stories that are independent?
Kris Hatcher relates how his team wrote and scored stories to keep them independent but still meeting acceptance criteria. When it comes to requirements, some teams have difficulty writing user stories that fit their specific necessary parameters.
Can a story be independent of an Excel report?
Before we learned the INVEST trick, we would have written a story to implement the export to Excel functionality on one of the reports, then written separate stories for each of the other reports, each of the successive stories having a dependency on the first one being completed. If we are writing stories to be independent, that cannot happen.
What’s the best way to make a story independent?
So, our first attempt to do things independently was to write, and score, each story so that it contained everything necessary to be completed. This worked well for the first story in the group, which was ranked by our product owner.
Is it possible to implement story without dependencies?
When dependencies come into play it may not be possible to implement a valuable story without implementing other much less valuable stories. Negotiable: A story is not a contract. A story IS an invitation to a conversation. The story captures the essence of what is desired.