Haven't posted for a while because at Big Corp we've been "requirement gathering". Big Corp is between processes now - and there's a big push for User Centered Design. As this all gets sorted out, we still have to deal with the old process. Old processes die hard.
So we still have Product Managers walking into meetings with lists of unrelated demands that they call "business requirements", devoid of any substantiation on how these things will help the end product. Here's a few examples:
- "Make the header on the weather larger"
- "Put 50 video links on the page"
- "Increase click through"
- "Make modules customizable"
Granular, disconnected requirements that are layered into the development process without an overall strategy will kill your product. Over time - sprint by sprint - the product will degrade in appearance, function, and ability to generate revenue. This is the requirement gathering junk pile.
That's what I've got for today.