Darrell Norton's Blog [MVP]

Fill in description here...

Requirements change

Requirements will always change. The changes will always cause you to redo existing code or have to write a lot more new code than you estimated. Changes never result in less work. The changes will always seem illogical. Requirements are never finished. Users change their minds faster than useless posts appear on the main feed.

I feel better now.

Published Jun 29 2004, 09:31 AM by darrell

Comments

Paul Laudeman said:

And very rarely does the *schedule* change to accomodate the ever changing requirements and rework...

# June 29, 2004 5:34 AM

Darrell said:

Schedule change? Isn't that an oxymoron? Heh.

# June 29, 2004 5:38 AM

Keith said:

Ya Scheduled Change.
It's Scheduled to Change the minute it's done.
:)

# June 29, 2004 6:12 AM

clarke ching said:

Requirements changes don't always cause rework ...
for instance, if the requirement hasn't been started yet.

Or, if requirements are descoped.

Am I taking your post to literally? Was it just a "gotta get this off my chest" sort of thing?

# June 29, 2004 6:25 AM

Darrell said:

Keith - that sums it up exactly.

# June 29, 2004 6:25 AM

Darrell said:

Clarke - it was sort of a rant post. It just seems the current project is always encountering escalatory changes.

And since we are down to the end of the schedule AND we're trying to clean up a mess left by other people (not my company), there is no such thing as a requirement that hasn't been started, at least in some sort of half-baked manner. :)

# June 29, 2004 6:31 AM

Jeff Key said:

I learned long ago that NOTHING is stable in software. Requirements, deadlines, teams -- you name it. Keeping your sanity in this business requires understanding that anything can and will change at any time. It sucks, but it's always been that way and will always be that way. (Although it doesn't suck any less when it happens. :))

# June 29, 2004 6:48 AM