This blog post defines the concept of use cases and user stories and discusses how and when they should be used in an Agile software development project. User stories are different from use cases because they are centred on the result and the benefit of the thing you’re describing, whereas use cases are more granular. The author recommends that you shouldn’t start writing use cases until the team specifically asks for them.
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