Adriana Beal has wrote an interesting post discussing four mistakes to avoid when leading a requirements meeting. The first mistake is to create unnecessary meetings and/or failing to recognize when one is needed. The second mistake is failing to prioritize the order in which items will be discussed, and whenever possible, the amount of time that will be dedicated to each item. The third mistake is to fail to keep the discussion on topic. The fourth mistake is failing to engage introverted or non-assertive people. Each mistakes is discussed in details in this blog post.
Four Mistakes to Avoid in Requirements Meeting
Reviewing Requirements for Testability
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 […]Read More
User Stories for Both Requirements and Testing
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, […]Read More
Understanding System Analysis Models
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.Read More