CodeBetter.Com
CodeBetter.Com
RSS 2.0 via Feedburner
           Do you Twitter? Follow us @CodeBetter

Raymond Lewallen

Framework Design, Agile Coach, President Oklahoma City Developers Group, Microsoft MVP C#, TDD, Continuous Integration, Patterns and Practices, Domain Driven Design, Speaker, VB.Net, C# and Sql Server

Communication is key - why I was misunderstood

Maybe you live in a cubicle.  You love your privacy, your personal space, your segregation from the rest of the office.  You have it decorated how you want and its your home away from home.  You have email and instant messengers at your fingertips to communicate with your co-workers.  What a wonderful world will live in, right?  You get to do all your work, communicate with your team and never have to leave the comfort of your private little “home”.

While this is all nice, it has a certain negative impact on your team’s ability to communicate and effectivly solve problems in a timely and cost-efficient manner.  For those of you who have knowledge of agile methodologies, XP in particular, you’re aware of the war room.  A war room is a large room where everybody on your team can sit together, see eachother, quickly and easily talk to eachother, have constant face to face communication and be a more effective team.

Face to face.  That is the key idea here.  Let me give you an example.  Check out this blog post and its responses.  I can guarantee, with absolute certainty, that none of the misunderstandings would have occurred, and this was have been a simple, easy discussion had we all been in the same room and able to communicate face to face.  When I finished writing the post, I re-read it to make sure I was communication my thoughts and purposes effectivly, and was satisfied with what I had.  Judging from a couple of the initial responses, I certainly failed to communicate my goals properly.  Had I taken Jeffrey’s initial advice, not only would this have not solved my problem effectively or achieved my overall goal, it may very well add complexity to the system (in my opinion) that doesn’t necessarily need to be there for that piece of the code to serve its function properly.  The same goes for Matt’s comment.  While its a fine way to create a private function to handle the logic of equating the dates, it serves little purpose to the overall goal I was trying to achieve.

Too many people think that emails, IM’s and blog posts with responses are an effective way to communicate.  While its convenient, its certainly not as effective as face to face communication.  Facial expressions and the ability to interject into a conversation can make all the difference in avoiding miscommunication and misunderstandings.

Get out of your cube, walk over, and have face to face conversations and ditch that internal IM and email crutch.  Its a crutch that will keep your communication efforts limping until you give it up.



Comments

Marcelo Mayworm said:

Hi Raymond,

nowadays I'm working in a offshore development, and it is a big challenge. I agree with about Face-to-Face. There are several situation, where we need to meet the others team, to guarantee that none of the misunderstandings could occurred.

I posted a blog about it http://weblogs.java.net/blog/mayworm/archive/2006/03/using_maven_to.html

- Marcelo
# May 9, 2006 3:30 PM

Samboy LIms said:

I worked in a Japanese firm before.   We did not have cubicles.   Employees sit around  large table.   You can say, they work face to face.
# May 10, 2006 12:50 PM

TobinTitus said:

That's interesting. I thought you were misunderstood because you didn't produce your post in smaller, more iterative chunks that could be shipped out from time to time.  
# May 10, 2006 5:17 PM

Leave a Comment

(required)  
(optional)
(required)  

Enter the numbers above:
Add

About Raymond Lewallen

Working primarily in the public sector during his career, Raymond has designed and built several high profile enterprise level applications for all levels of the government. Raymond now works as a solutions architect for EMC. Raymond is an agile coach, Microsoft MVP C# and also president of the Oklahoma City Developers Group and Oklahoma Agile Developers Group. Raymond spends a lot of his time learning and teaching such things as Test Driven Development, Domain Driven Design, Design Patterns and Extreme Programming practices and principles, to name a few. Raymond is also an advocate of Alt.Net. Raymond is primarily a framework guy, so don't ask him anything about UI :) Check out Devlicio.us!