From Value to Solutions in Agile

Requirements Management Blogs

Agile uses mostly user stories to capture requirements. In his blog post, Jean-Jacques Dubray explains that there is a problem with user stories because they tend to focus on the solution and not on the problem definition.

User stories are base on actions and actions are solution centric and should not be part of the problem definition. Jean-Jacques Dubray suggests that “we make a very simple and easy change to Agile and replace “user stories” by “problem statements”. Each problem must be “solutioned”, either by decomposing it into simpler problems or solutioning it directly.”

This post is completed by a very valuable comment from Mike Cohn who wrote that “User stories are not meant to be the high-level thinking about a product. They are an output of that thinking. That is, a product owner should convene a meeting with individuals who can help solve a problem.”

Read the complete post on http://www.ebpml.org/blog2/index.php/2013/04/26/reinventing-agile-from-value-to

Requirements Management Blogs
Blogs Knowledge

Find Missing Requirements

This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.

Read More
Requirements Management Blogs
Blogs Knowledge

Perfect Requirements

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
Requirements Management Blogs
Blogs Knowledge

Why Should You Write Requirements

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 More

Copyright © 2009-2022 Martinig & Associates