Absolutely no disrespect intended - when working with planets on our Solar system, there are clearly limited choices. Anyway...
Given the two groups are different in so many ways, how have we ever believed that a requirements document would magically span this gap, bringing the two parties together in everlasting harmony? Realizing that the only way to get men and women (oops, the Mars, Venus thing), I mean programmers and users to communicate, was to implement an development "asset" that was anything but a static document.
Call it a user story, feature, backlog item, or whatever, but let's always remember its one of its primary purposes to to facilitate communication. By engaging both developers and customers in a conversation before and during development, all kinds of good things can result within the software.
Comments