[…] Kevin talks in particular about how to communicate with different team members as part of incorporating UI designs into the finished product – by understanding that you need to communicate with people in the language to which they are accustomed. I just wrote about this same topic at a general level in my recent post, Intimate domains. Kevin provides great specific suggestions along the same vein. […]
[…] The goal of writing a requirement is not pedantic accuracy, it’s effective communication. In addition to crossing domain-boundaries with the different audiences that consume our requirements, we often are crossing language barriers and varying educational levels. It’s hard enough conveying concepts that presume contextual knowledge, our readers shouldn’t have to parse the text repeatedly. […]
Scott Sehlhorst said,
December 28, 2005 at 10:59 pm
Marcus has posted a complimentary article on his site at http://rationalizedthoughts.blogspot.com/2005/12/why-of-business-analysis.html
It’s worth a read
Tyner Blain » More on talking to your audience said,
January 4, 2006 at 12:12 am
[…] Kevin talks in particular about how to communicate with different team members as part of incorporating UI designs into the finished product – by understanding that you need to communicate with people in the language to which they are accustomed. I just wrote about this same topic at a general level in my recent post, Intimate domains. Kevin provides great specific suggestions along the same vein. […]
Tyner Blain » Readability and requirements said,
January 4, 2006 at 2:39 am
[…] The goal of writing a requirement is not pedantic accuracy, it’s effective communication. In addition to crossing domain-boundaries with the different audiences that consume our requirements, we often are crossing language barriers and varying educational levels. It’s hard enough conveying concepts that presume contextual knowledge, our readers shouldn’t have to parse the text repeatedly. […]