Managing Agile Requirements

Requirements Management Articles

People often believe that Agile software development requires not documentation. Even if the Agile Manifesto values “Working Software over Comprehensive Documentation”, you should note the word “over” in this statement. The Manifesto is not recommending no documentation, but stating a preference for working software over documentation.

This article presents the Agile requirements definition and management (RDM) framework that can be used for just-in-time requirements definition or to build a repository of requirements for future use. It was specifically designed to achieve the business goal to make sure that they feed the product backlog and can support and describe what needs to be built by the development team prior to the start of the sprint.

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 Articles
Articles Knowledge

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

Copyright © 2009-2022 Martinig & Associates