Comments on: We Don’t Need No Stinkin’ Requirements http://www.pathf.com/blogs/2007/08/we-dont-need-no/ Running commentary about agile development, user experience design and Ajax. Mon, 01 Dec 2008 20:52:36 +0000 http://wordpress.org/?v=2.5.1 By: Anonymous http://www.pathf.com/blogs/2007/08/we-dont-need-no/#comment-801 Anonymous Mon, 10 Sep 2007 04:20:25 +0000 http://www.pathf.com/blogs/2007/08/we-dont-need-no/#comment-801 <p>mojojojo: Yes, requirements in the Agile process are much more loose and informal than in, say, a waterfall process. Think of them as "just enough" requirements. And I've been on teams where the iterations are of two-week durations with a *release* being 4 iterations or 2 months. Once the Agile process is adapted to the team (or vice versa), I think the process works very well. You just have to be comfortable with not knowing everything about everything.</p> <p>Davo: I believe we call that a grad school project. :)</p> mojojojo: Yes, requirements in the Agile process are much more loose and informal than in, say, a waterfall process. Think of them as “just enough” requirements. And I’ve been on teams where the iterations are of two-week durations with a *release* being 4 iterations or 2 months. Once the Agile process is adapted to the team (or vice versa), I think the process works very well. You just have to be comfortable with not knowing everything about everything.

Davo: I believe we call that a grad school project. :)

]]> By: David http://www.pathf.com/blogs/2007/08/we-dont-need-no/#comment-800 David Fri, 07 Sep 2007 16:08:35 +0000 http://www.pathf.com/blogs/2007/08/we-dont-need-no/#comment-800 <p>No requirements? A consultants dream! Where do I sign up?</p> <p>Davo</p> No requirements? A consultants dream! Where do I sign up?

Davo

]]> By: mojojojo_ http://www.pathf.com/blogs/2007/08/we-dont-need-no/#comment-799 mojojojo_ Fri, 07 Sep 2007 05:15:30 +0000 http://www.pathf.com/blogs/2007/08/we-dont-need-no/#comment-799 <p>Correct me if I'm wrong, but one of the things I remember about Agile Developement is the fact that REQUIREMENTS for the project are written, but the difference is that they are more loose and informal AND basically are not that precise (the developement is done in iterations no longer than 3 months and above those 3 months no planning is made, it is argumented by the fact that financial market as well as other factors to consider change and going beyond that time frame may lead to maladjustment with the status quo which changed during that time.</p> Correct me if I’m wrong, but one of the things I remember about Agile Developement is the fact that REQUIREMENTS for the project are written, but the difference is that they are more loose and informal AND basically are not that precise (the developement is done in iterations no longer than 3 months and above those 3 months no planning is made, it is argumented by the fact that financial market as well as other factors to consider change and going beyond that time frame may lead to maladjustment with the status quo which changed during that time.

]]>