As he is responsible to create the requirements, we set the customer as the sole owner of the definition of success. Therefore, we force the burden of success onto the shoulders of the very person who has come to us, the software developer, for help. If that isn’t evil incarnate? This post is about the fact that in the hands of a master software developer requirements are both carrot and stick.
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
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read More
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 MoreCopyright © 2009-2022 Martinig & Associates