Knowledge
Software Requirements Management Articles, Blog Posts, Books and Quotes
Using Approval Branching for Business Requirements
When the business changes rapidly, this is a problem for a development team that has in its current release trunk both approved and unapproved features. In this blog post, Jack Low presents a solution to minimise the issues created by unapproved features in the codebase at the time of a release and contrasts this approach […]
Read More
Creating a User Story Map
A user story map is a technique created by Jeff Patton where you arranges you user stories into a useful model to help understand the functionality of the system. In this blog post, Steve Rogalsky explains how to create a user story map.
Read More
Asking Open-Ended Questions
Getting the important business needs out of the requirements gathering process should be the goal of every business analyst. In this article, Karl Wiegers discusses the benefits of asking open-ended questions during requirements specification. They are especially useful to discover exceptions to the normal process behaviour. You are then able to determine and describe how […]
Read More
Writing Better Requirements with Examples
Gathering requirements for software development is not always easy and IT guys will often complains that customers have difficulties to express what they want to achieve with a new development project. In this blog post, Lars Hoidahl discusses this topic and explains how examples and screen sketches can help to write better requirements.
Read More
User Stories That Are Too Big
In this blog post, Jeffrey Davidson discusses the fact that a common issue for Scrum teams is that their user stories are too big. He explains that many teams ask for larger stories because they don’t know how to slice the work into smaller pieces. Writing smaller user stories will make your team happier and […]
Read More
Minimal Viable Products
In this blog post, Cory Foy discusses how to apply the Pareto law, the famous 80/20 rule, to the concept of minimal viable product. He defines two starting positions: you have to sell a solution for a problem or there is an actual need in a market. A Standish research shows that 45% of the […]
Read More