Comments on: Why requirements stink http://www.scottberkun.com/blog/2009/why-requirements-stink/ Management and Creative Thinking Thu, 18 Mar 2010 09:37:07 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: Mark’s Blog » Blog Archive » Getting Real - by 37signals http://www.scottberkun.com/blog/2009/why-requirements-stink/comment-page-1/#comment-544468 Mark’s Blog » Blog Archive » Getting Real - by 37signals Wed, 13 May 2009 18:59:19 +0000 http://www.scottberkun.com/?p=1600#comment-544468 [...] Real” from 37signals. I bought the book when I read about it on a blog from Scott Berkun (Why Requirements Stink) [...] [...] Real” from 37signals. I bought the book when I read about it on a blog from Scott Berkun (Why Requirements Stink) [...]

]]> By: Pulitzer winner’s key lesson learned: Demos, not memos « Internet Turnkey Websites http://www.scottberkun.com/blog/2009/why-requirements-stink/comment-page-1/#comment-542268 Pulitzer winner’s key lesson learned: Demos, not memos « Internet Turnkey Websites Fri, 08 May 2009 02:21:25 +0000 http://www.scottberkun.com/?p=1600#comment-542268 [...] also links to “Why requirements stink” which offers this great example: “Here’s a requirements list: Make a $5 car that goes 500 [...] [...] also links to “Why requirements stink” which offers this great example: “Here’s a requirements list: Make a $5 car that goes 500 [...]

]]> By: Dave Peele http://www.scottberkun.com/blog/2009/why-requirements-stink/comment-page-1/#comment-539300 Dave Peele Thu, 30 Apr 2009 14:15:19 +0000 http://www.scottberkun.com/?p=1600#comment-539300 Good article! I like the idea of collaboration on the requirements document, especially after a recent project that went rather un-smoothly due to problems with the initial spec. I do have one question that brings up another issue... In my experience, the provided spec or requirements doc has been our primary tool for estimating projects. In your suggestion, the spec/doc should come after project starts and therefore after the initial estimate. Project based billing has been our primary method thus far and we are transitioning away from that. My questions is... What are your thoughts on the best way to handle estimates without a spec/doc? And your thoughts on project billing vs. hourly billing? Good article! I like the idea of collaboration on the requirements document, especially after a recent project that went rather un-smoothly due to problems with the initial spec. I do have one question that brings up another issue…

In my experience, the provided spec or requirements doc has been our primary tool for estimating projects. In your suggestion, the spec/doc should come after project starts and therefore after the initial estimate. Project based billing has been our primary method thus far and we are transitioning away from that. My questions is… What are your thoughts on the best way to handle estimates without a spec/doc? And your thoughts on project billing vs. hourly billing?

]]>