There are different popular models for collaborative software requirements definition. In this article, Gojko Adzic, the author of Specification by Example, discusses some of them. Big specification workshops, like Product Backlog Refinement (PBR) workshops, with the entire team allows building a shared understanding and produce a set of examples that illustrate a feature. Smaller workshops that involve one developer, one tester, and one business analyst are called Three Amigos meeting. Teams where business users and stakeholders sit close by (and are readily available to answer questions) have great results with informal conversations. Instead of having big scheduled workshops, anyone who had a stake in a story would briefly meet before starting to implement it.
Collaborative Requirements Definition
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 MoreUnderstanding 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 MoreFind Missing Requirements
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read More