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.”
Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]
User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective. They’re a good basis for test cases, so as to support integrated requirements management and testing. In this article, […]
This article is an extract of the “Complete Systems Analysis” written by James and Suzanne Robertson. It explains the basics of analysis models and emphasize that the important thing to remember is that modeling tools are complementary. Each shows one aspect of the system. Together, they make a complete working model of the system.