Planning Implementation
Peter Middleton, James Sutton · Productivity Press eBooks · 2020
Traditional requirements make little if any note of priority. Requirements are written as “shalls,” as in “the software shall sort all input fields. The developers simply present the compiled list of values to each customer and ask them to place each value into one of three categories or piles, based on whether the value is of low, medium, or high importance. Risk is the possibility that we will lose some business positioning or project circumstance that is favorable to us. The cost of changing the order of value implementation is miniscule compared to the cost of changing the values themselves. Each change of a value, or a requirement in traditional projects, causes repeated downstream development work; the later the change, the more work. Extreme Programming has some excellent ideas that can be applied to almost any value-driven development. Value resolution in the customer space early on is the main foundation for lean software production.