Available on Amazon.com
The acronym INVEST is used to describe a Feature.
The Feature is a piece of software that is
“independent, negotiable, valuable, estimateable, small and testable.”
It is a unit of work that meets a specific customer need and can be built within a short software development cycle.
The problem is, how do we document the Feature so that it can be determined if it actually fits the INVEST rule before
we embark on a build plan?
The Feature Model is the answer. More than a User Story, less than a Requirements Specification, the Feature Model minimizes redundant conversations by consolidating the questions and answers into one cohesive software model. Now, the request can be visualized to see if it really meets the INVEST rule. If it passes the test, then the model is presented to the development team as a request to build. The model itself is designed to be as lean as possible while pulling together just enough information to create the Feature.
The Feature Model is the answer. More than a User Story, less than a Requirements Specification, the Feature Model minimizes redundant conversations by consolidating the questions and answers into one cohesive software model. Now, the request can be visualized to see if it really meets the INVEST rule. If it passes the test, then the model is presented to the development team as a request to build. The model itself is designed to be as lean as possible while pulling together just enough information to create the Feature.
| Project Id: | Contact: Mike Brennan |
| thStickman@yahoo.com | |
| (864) 641-1732 |