Ordering the Product Backlog

Requirements Management Articles

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.”

software requirements group
Articles Knowledge

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
Requirements Management Blogs
Blogs Knowledge

Find Missing Requirements

This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.

Read More
Requirements Management Blogs
Blogs Knowledge

Perfect Requirements

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 More

Copyright © 2009-2022 Martinig & Associates