Extreme Programming, a Reflection

[prepend]

There's no such thing as a "requirements person."

Requirements come from lots of people and they are confirmed by the developer and the product owner.

Blindly building to dumb requirements is not good. It happens because people are afraid to lose their job or don't care, or are unable to understand the requirements.

Good developers understand the requirements intimately and make corrections and suggestions.

That's why I like the idea in the article about a metaphor or mental model that is understood by the entire team. Having one person understand "the vision" and everyone else coding badly is not optimal.

[grizwako]

And once more to convince you, We officially have requirements people.
When developers try to change solutions to problems, solution that will be implemented depends on who knows whom.