Comments on: Using A Wiki To Replace Requirements And Produce Documentation For Your Agile Projects http://www.davidwhitney.co.uk/Blog/2009/04/07/using-a-wiki-to-replace-requirements-and-produce-documentation-for-your-agile-projects/ Just another WordPress weblog Wed, 08 Feb 2012 08:18:04 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Lee Englestone http://www.davidwhitney.co.uk/Blog/2009/04/07/using-a-wiki-to-replace-requirements-and-produce-documentation-for-your-agile-projects/comment-page-1/#comment-90 Lee Englestone Mon, 20 Apr 2009 20:15:50 +0000 http://www.davidwhitney.co.uk/content/blog/?p=138#comment-90 I agree. You need requirements. I'm amazed at the number of people that don't 'get it' as you put it. Would you ask someone to build you a house without architect plans? as that's effectively what your're doing. Well actually it's more like not stating how many windows your want, how many stories, what colour. Same diff you'd end up with a crappy house that's not what you wanted. You also need the right people coming up with the requirements for a project and that means 'buy-in'. Without buy-in from main stakeholders requirements are flawed. I'm shocked when the wrong people compile the requirements. Cringe. Bad requirements = Bad solution. -- Lee I agree. You need requirements. I’m amazed at the number of people that don’t ‘get it’ as you put it. Would you ask someone to build you a house without architect plans? as that’s effectively what your’re doing.

Well actually it’s more like not stating how many windows your want, how many stories, what colour. Same diff you’d end up with a crappy house that’s not what you wanted.

You also need the right people coming up with the requirements for a project and that means ‘buy-in’. Without buy-in from main stakeholders requirements are flawed. I’m shocked when the wrong people compile the requirements. Cringe.

Bad requirements = Bad solution.

– Lee

]]>