[OriginalSyn]

Exactly, I can't count the times I've butted heads with our marketing, design and business development teams over silly, annoying and outright ridiculous features they had charged us with implementing... before we became a more agile shop these confrontations usually resulted in me having to back down and implement the features because they were pretty much set in stone by the time they got into our queue but now we can often compromise since we're involved earlier in the planning stages.

[davimack]

I wouldn't attribute the change to "agile" ... but would attribute the problem to poor design. Subtle difference, but you get the same garbage in agile stuff - just depends on the PM, really.

[OriginalSyn]

No, I don't attribute it to being agile, I attribute it to dev being involved near the start of project planning and having input along the way. It just happened that when the company decided on being an agile shop this happened as well. Sorry that was not clear.