In this article, Brent Reid discusses the fact that in Scrum, the product backlog should be ordered and not prioritized. His point is that priority has a meaning only within a certain context. Thus what is high priority one day could be low priority in the future. Thus, the product owner must deliver a totally ordered Product Backlog, even if it is difficult to make such decisions. However, as Brent Reid wrote it: “this clearly places the responsibility of resolving the problem on the product owner instead of on the development team, which may not have a good understanding of these competing priorities.”
Ordering the Product Backlog
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