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 communicate requirements in a way that will make the developers more productive is for the Product Owner to write requirements as user stories.
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read More
In this blog post, James Christie starts from the fact that perfect requirements don’t exist to discuss the idea that the quality of requirements is directly influenced by the time and money you invest in crafting them.
Read More
In this blog post, By Scott Sehlhorst starts with a simple fact: if there is a lot of discussions on how to write requirements, there is not so much material on why to write requirements. His advice is that you should start by thinking about why you write requirements before you decide how to write […]
Read MoreCopyright © 2009-2022 Martinig & Associates