Comments on: Techniques for Gathering Requirements http://pmstories.com/2008/01/29/requirements-gathering-techniques/ A blog about smarter software engineering and project management Fri, 12 Mar 2010 13:07:32 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Top Methods for Gathering Requirements « P.M. Tips and Tricks http://pmstories.com/2008/01/29/requirements-gathering-techniques/comment-page-1/#comment-8063 Top Methods for Gathering Requirements « P.M. Tips and Tricks Tue, 08 Sep 2009 18:14:58 +0000 http://pmstories.com/en/2008/01/29/requirements-gathering-techniques/#comment-8063 [...] for gathering requirements is a must-read.  As a rebuttal to that article, here’s another list of techniques to gather project requirements.  Looking at the goal from the other end, AC offers How to give the [...] [...] for gathering requirements is a must-read.  As a rebuttal to that article, here’s another list of techniques to gather project requirements.  Looking at the goal from the other end, AC offers How to give the [...]

]]> By: Техники за събиране на изисквания : PM Stories http://pmstories.com/2008/01/29/requirements-gathering-techniques/comment-page-1/#comment-89 Техники за събиране на изисквания : PM Stories Tue, 05 Feb 2008 18:10:13 +0000 http://pmstories.com/en/2008/01/29/requirements-gathering-techniques/#comment-89 [...] Този пост е достъпен и на английски език.  [...] [...] Този пост е достъпен и на английски език.  [...]

]]> By: Michael Wilkes http://pmstories.com/2008/01/29/requirements-gathering-techniques/comment-page-1/#comment-87 Michael Wilkes Wed, 30 Jan 2008 15:47:05 +0000 http://pmstories.com/en/2008/01/29/requirements-gathering-techniques/#comment-87 I so agree that prototyping is a great way to give the customer (and developers too) a clear picture of what will be built. Seeing is believing! I would argue that it is no longer expensive, however. Modern non-programmer tools like Axure make it easy to do and we all know that, in the long run, clarity in the beginning saves money in the end. Getting a blueprint from an architect can be considered a significant expense, but no one would consider building a home without one. A prototype is the closest thing we have to a "model home" in the software world. I always encourage the use of prototypes now, even for enhancements. I so agree that prototyping is a great way to give the customer (and developers too) a clear picture of what will be built. Seeing is believing! I would argue that it is no longer expensive, however.

Modern non-programmer tools like Axure make it easy to do and we all know that, in the long run, clarity in the beginning saves money in the end.
Getting a blueprint from an architect can be considered a significant expense, but no one would consider building a home without one.

A prototype is the closest thing we have to a “model home” in the software world. I always encourage the use of prototypes now, even for enhancements.

]]>