Requirements Quote

from Ron Jeffries on the Agile Testing board

I think "requirements" always means approximately "what we think, right now, that we need".

 

One of my pet peeves working in development is dealing with the waterfall-ish idea that requirements and analysis is done just because you clicked print on a Word document. 

About Jeremy Miller

Jeremy is the Chief Software Architect at Dovetail Software, the coolest ISV in Austin. Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy is the author of the open source StructureMap tool for Dependency Injection with .Net, StoryTeller for supercharged acceptance testing in .Net, and one of the principal developers behind FubuMVC. Jeremy's thoughts on all things software can be found at The Shade Tree Developer at http://codebetter.com/jeremymiller.
This entry was posted in Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • http://www.codebetter.com/blogs/jay.kimble jkimble

    While I would not call myself an agilist, I totally agree with this statement (it’s one of the things about agile methods that intrigue me). In my 14 years of professional development, I’ve worked on a large number of projects/features where YAGNI didn’t rule. As an independent, I’ve been working hard on my sales pitch for a flat rate (and this is the cornerstone of it).

  • http://www.edmblog.com James Taylor

    Part of the problem is that requirements are a tarpit for programmers and separating out rules and requirements will make life much easier for programmers.

  • http://www.jenswinter.com Jens

    *sigh*…If only I could teach my manager…