Feature Injection is a process to help guide Agile Business Analysts. It is formed of three steps*:
- Hunt the Value ( An adaptation of value from “The Goal” )
- Inject the Features ( Value Stream Mapping )
- Break the Model ( Inspired by Kolb’s Circle of Learning and Test Driven Development )
- Reduce User Costs / Increase Return on Investment ( UX Metrics )
* Kent McDonald originally devised the three steps.
Feature Injection is a variant form of Value Stream Mapping that adds steps 3 and 4, and explicitly calls out step 1. “Hunt the value”. Without step one, there is a possibility that the “Value Stream Mapping” will create a local optimisation of the process. Hunt the value ensure that the system optimisation is not localised. Some users of Value Stream Mapping start in the middle in their part of the process. As a result they may inadvertently create a local optimisation. They may also start from the beginning of the process and work forward rather than work backwards which slows the process as you need to keep checking decisions against the value being delivered.
Step 1 of value stream mapping is to identify the value. If you do not know what the value is, how can you map the value stream. If you do not start with finding the value, you are not performing value stream mapping. As the value is always in the outcome, you have to start at the output and work back to the inputs in order to optimise the value stream.
This was first documented in comic strips that were published on Agile Journal by Amr Elssamadisy. These strips were collected into “Real Options at Agile 2009” that is available here.