Remember in \u2018the old days\u2019, you would write a letter to a friend describing your recent trip: the experience, the exhilaration, how relaxed you felt? A few days later your friend would receive it, and maybe a few days later they would write back, and then a few weeks after you sent your letter, you might get one in return.<\/p>\n\n\n\n
Then we moved to email. Email is faster than writing and mailing a letter. It\u2019s the same experience, just faster.<\/p>\n\n\n\n
Describing something by writing it down is low bandwidth communication. You can read the words and hopefully understand what the person is trying to get across. It\u2019s very hard to experience expressions, feelings, or other intangible elements that add to your experience. It\u2019s also very easy to misunderstand what the writer is actually trying to express.<\/p>\n\n\n\n
Imagine that letter or email exchange as a phone call instead. You can hear real excitement in the person\u2019s voice; you can interject with questions; you can ask for clarifications; and you can repeat back to the storyteller your understanding \u2013 so that they know that you got it.<\/p>\n\n\n\n
Phone calls are medium-bandwidth communication \u2013 they are certainly better than written communication in terms of getting your point across, but they lack a certain aspect of expressiveness that can only come across in a face-to-face conversation.<\/p>\n\n\n\n
If you are sitting in front of someone, seeing the same things that they are, experiencing the same outside factors as they are, reading their body language and expressions, then you are truly having high-bandwidth communication. We get the most out of this type of communication \u2013 it is the quickest, most honest, and best way to ensure that all parties really understand one another.<\/p>\n\n\n\n
Which brings me to software development, in particular the requirements gathering process. Sure, in the software development lifecycle (SDLC) written documentation is important, but only to document what has been agreed on. You cannot create good requirements documents without going through a series of sessions of high-bandwidth communication \u2013 all the stakeholders need to be in the same room brainstorming, sketching, modeling, asking and answering the hard questions in order to get a true picture of what needs to be built.<\/p>\n","protected":false},"excerpt":{"rendered":"
Remember in \u2018the old days\u2019, you would write a letter to a friend describing your recent trip: the experience, the exhilaration, how relaxed you felt? A few days later your friend would receive it, and maybe a few days later they would write back, and then a few weeks after you sent your letter, you […]<\/p>\n","protected":false},"author":8,"featured_media":3557,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,13],"tags":[],"yoast_head":"\n