Can good requirements ever be defined?

If Architects Had To Work Like Programmers
I ran across this old chain email and it came at a time when I was thinking about software requirements. I'm continually hearing complaints from developers about how the "requirements" are always changing which causes rework and delays. I've never really felt this pain in my own development, and I think I now realize why. I use a very iterative development approach. I create prototypes and mock-ups and demo sites for my users to actually see what the software will look like, and I let them adjust the requirements based on that. Obviously there are whole methodologies built around this iterative premise, but I think I'm just now seeing it as part of the solution to the "requirements" problem. Build it small and then fix it, because you're going to have to fix it either way.

Looking for Jason Penney

I loyal reader is looking for a Jason Penney (not me) that he met in Punta Cana. If you're ego-surfing and come across this website, maybe you'll be the right Jason Penney. Here's his request.

I'm looking for a Jason Penney. We planned 5 years ago to get a drink this year in New York city. I had his adress but he moved. so please help. He was in New York and he was also a photographer. I met him in Punta Cana. Thanks
kmartk2@yahoo.ca-NOSPAM

Just remove the -NOSPAM to email him.

Is your name Jason Penney

If so, add a comment. Of course, that's assuming the comments even work.

Nothing to see here...

You can move along folks.

If you want to see something here, try posting an idea in the comments.