I look forward to your agile extremists article, David. Problems arise whenever people take extremely polar positions and defend them to the death. "We're agile! We can change direction on a dime! We don't need to write anything down -- what a waste! We just have conversations about stories and then communicate telepathically!" Or, "We're engineers! We record all of the requirements in great detail right now and they will never change because we'll get it right the first time! We don't need no stinkin' changes!"

Both of those extreme positions are unrealistic. So is discarding existing effective techniques because someone thinks that they don't apply anymore. So is assuming that any team member can effectively perform any function -- specialists (like BAs) no longer needed. So is inventing new terminology to divorce oneself from the past and create a new mystique.

A more realistic mindset recognizes that somewhere in between the extremes is most sensible, based on the nature of the project, team, culture, customers, constraints, and risks. Having flexible, adaptable processes is as helpful as having flexible, adaptable team members.

BTW, that statement was kind of a hot button for my, as I've written 5 books on software requirements. :-)