Yeah, I like the idea too. It might also have a nice byproduct of forcing you to name features and assign value to them. Testing in general forces you to think through the value and arrangement of code, but features kind of get lost and messy, and we might support features not delivering value, but we don't really draw the line.
A technologist currently working in eHealth, loves to code, grow new developers and solve new problems leveraging old technology approaches.
I love opensource & knowledge sharing
Location
Kampala, Uganda
Education
BSc Civil Engineering
Work
Problem Solver and Solutions Strategist at Styx Technology Group
Yeah, I like the idea too. It might also have a nice byproduct of forcing you to name features and assign value to them. Testing in general forces you to think through the value and arrangement of code, but features kind of get lost and messy, and we might support features not delivering value, but we don't really draw the line.
And features could also be proxied by user stories - which have an element of value, and acceptance criteria as part of their documentation.
This can also be tied with metrics on how features are used to get a better insight