Successful Feature Injection

Requirements Management Articles

Feature injection is a business analysis approach that focuses on business value, an approach similar to Behavior Driven Development (BDD). It transfers knowledge to the team about how the project can deliver value and what are the features needed to deliver that value. Examples are used to transfer this information to the team in the form with the goal to eliminate the waste of separate requirements specifications and tests. Why is it call Feature Injection? Because “The process of pulling value from a project injects features into the system”.

This article provides an overview of Feature Injection and related techniques. It explains the key elements of the framework with the support of a realistic example. High level examples provide enough context to focus related development processes such as Test-Driven Development (TDD) and Behavior-Driven Development (BDD). They can be broken down into smaller, finer grained examples that describe how different functions of a system need to work in order to support the high level examples. If they are detailed enough, the examples can also be automatically validated against a system in development, providing an objective measure of progress and a foundation for a living documentation system.

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

Why Should You Write Requirements

In this blog post, By Scott Sehlhorst starts with a simple fact: if there is a lot of discussions on how to write requirements, there is not so much material on why to write requirements. His advice is that you should start by thinking about why you write requirements before you decide how to write […]

Read More

Copyright © 2009-2022 Martinig & Associates