Darrell Norton's Blog [MVP]

Sponsors

The Lounge

Wicked Cool Jobs

Syndication

Recent Posts

Tags

View more

News

  • Darrell Norton pic

    MVP logo

    View Darrell Norton's profile on LinkedIn

    Currently Reading:

    weewar.com

.NET User Group

Articles

Archives

Advertisement

Darrell Norton's Blog [MVP] » Requirements change
Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
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.

Posted Tue, Jun 29 2004 9:31 AM by Darrell Norton

[Advertisement]

Comments

Paul Laudeman wrote re: Requirements change
on Tue, Jun 29 2004 5:34 AM
And very rarely does the *schedule* change to accomodate the ever changing requirements and rework...
Darrell wrote re: Requirements change
on Tue, Jun 29 2004 5:38 AM
Schedule change? Isn't that an oxymoron? Heh.
Keith wrote re: Requirements change
on Tue, Jun 29 2004 6:12 AM
Ya Scheduled Change.
It's Scheduled to Change the minute it's done.
:)
clarke ching wrote re: Requirements change
on Tue, Jun 29 2004 6:25 AM
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?
Darrell wrote re: Requirements change
on Tue, Jun 29 2004 6:25 AM
Keith - that sums it up exactly.
Darrell wrote re: Requirements change
on Tue, Jun 29 2004 6:31 AM
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. :)
Jeff Key wrote re: Requirements change
on Tue, Jun 29 2004 6:48 AM
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. :))
Darrell wrote re: Requirements change
on Tue, Jun 29 2004 6:58 AM
Amen!
Devlicio.us