User Stories Acceptance Criteria

Requirements Management Articles

In Scrum user stories are the starting point of a conversation. This articles discusses the challenge for the Product Owner to provide acceptance criteria to help the Scrum team understand user stories. The author explains that acceptance criteria need not constitute an exhaustive list, but they should be sufficient to move forward. Acceptance criteria are temporal in nature, because they are the functionality the product owner had in mind at a distant time in the past. Acceptance criteria become refined with sprint progress through each story iteration. Acceptance criteria can never be complete, as they embody expectations that change over time.

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