Minimal Viable Products

Requirements Management Blogs

In this blog post, Cory Foy discusses how to apply the Pareto law, the famous 80/20 rule, to the concept of minimal viable product. He defines two starting positions: you have to sell a solution for a problem or there is an actual need in a market. A Standish research shows that 45% of the features of a product are never used. This are the features you should not create if you want to deliver your product quickly.

The key definition of Minimal Viable Products is that you know the highest value features, so you build and ship those first. Incremental releases allow gaining experience to improve the product. If you are filling a void in a market, he jokes that you should create initially a product with unwanted features, because when customers are irritated, you will learn quicker.

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