user stories
Functional Requirements Are Not Always User Stories
What happens when Scrum projects do not have clear user stories? Because Product Owner has the subject matter expertise and decision making capabilities, that does not mean that he can clearly communicate the requirements in a way that will make the developers/testers as productive as possible. This blog post explains that the best way to […]
Read MoreUser Stories Lifecycle
In this blog post, Henrik Larsson explains the lifeycle of user stories from the Release planning meeting to the release tracking stage where the product owner checks if the release date and contents can be kept.
Read MoreA User Story Primer
This article explains the application of Scrum user stories. In agile development, the user story is a lightweight and more nimble substitute for what has been our traditional means of specifying software requirements – software requirements specifications, use case specifications, etc.
Read MoreCommon User Stories Mistakes
In this article, Krystian Kaczor explains that expressing requirements as user stories causes a lot of trouble to Scrum teams. He shares the five most common mistakes people make writing user stories.
Read MoreUser Story Length
Story writing is usually taught now as a singsong “As a I want so that .” The writer should then immediately document acceptance criteria in the form of a constraint list or automated acceptance tests. Many consider it poor form to create a story that someone outside the team can’t understand from its documentation alone. […]
Read MoreUser story vs use case vs “what are we trying to accomplish”
In this blog post, Leon Kotovich explains that requirements are not about user stories or use cases, but that you should use all available techniques to solve your problem correctly once you have defined it.
Read More