
A good reminder that not everything requested add value, and could even detract (huge amounts of wasted paper in this example). It shows that it is as important to understand the value of requirements as it is to understand the requirement itself. In fact, something we've started doing recently is adding a 'benefits' column next to each requirement captured to allow those details to be noted and shared with others, creating meaning to requirements, and therefore stronger collaboration on solutions.
http://www.economist.com/node/18529895
Sources and Credits -
Thanks to Cherky for sharing the article with me
http://www.economist.com