Business value approach to requirements #

“Chris Matts”:https://abc.truemesh.com/ “points”:https://abc.truemesh.com/archives/000306.html to a paper he co-authored with “Andy Pols”:https://www.pols.co.uk/blog/index.html on “Business Value-driven Software Development”:https://www.pols.co.uk/business-coach/BusinessValueDrivenDevelopment.pdf (PDF) Sounds like obvious common sense to me, which presumably means it doesn’t happen as much as it could in the real world! 🙂

In “another post(Documents Create Antagonism)”:https://abc.truemesh.com/archives/000305.html he also puts his finger on a common problem with “Big Design Up Front”:https://c2.com/cgi/wiki?BigDesignUpFront projects – namely the dysfunctional behaviour driven on both business and development sides of a project by too much early specification that does not consider the value of requested features.

Avatar
Julian Elve
Proactive application of technology to business

My interests include technology, personal knowledge management, social change

Next
Previous