Extreme Programming Values – Communication

This content is syndicated from VersionOne by VersionOne. To view the original post in full, click here.

Communication is one of the most underestimated of the XP values.  The value of communication is not underestimated, so much as how hard it is.  There are many different ways to believe we are truly communicating, but they so often fall short.  When we are talking about software development,  we have even more communications models to consider.

One of the most obvious is face to face, just plain talking to each other.  I still feel that this is the best, most effective way to communicate.  This is why co-located teams are always the preferred mechanism for agile development.  Not only are we able to have a real-time understanding of what someone is saying, we are able to pick up on subtle body language and nuance that may or may not come out in the written form.  When communicating face to face, we still need to be aware of what we are saying and how we are saying it.  We still need to do our best to remember the context around the conversation, and ensure we are actually hearing what is being said.  I have many times had a conversation where I reflected back what I thought I had heard, only to have the speaker say "no, that is not what I said."  This is common enough that I encourage everyone to avoid assuming they understood something, but to actually confirm that they did.

I am definitely a fan of the written word.  Even so, it has its drawbacks.  To a certain extent,agile documentation when I write something, I am talking *at* you, not *with* you.  There is no space for refinement, at least not instantaneously.  It's a little better with tools like IM, which is at least qausi-real time, but still falls short on nuance.  In the end we discover that for actual communication, written documents are far less effective than any other form.

So what about those forms of communication that are so important to agile software development?  How do we communicate with our stake holders, customers, and development teams?  So often we choose some sort of document.  We write up a very large requirements document, from which we create a specification document, which will then have a design document attached.  Finally, we will write some code and create the working software.

Along the way, we will spend a lot of time going over these documents.  We will have meetings to discuss them.  We will create drafts that we will meet over and refine.  Only when we are finally convinced that we have a particular document right will we move to the next step in our documentation.  Now, I've been to a lot of these meetings, and it always turns out the same way.  If we allocate, say an hour, to the meeting, the first 45 minutes will be discussing whether or not we have used the correct format, filled in the right blanks at the right time, and generally done everything we can to satisfy the documentation standard.  The last 15 minutes, if we can, we will talk about the actual content.

At some point in this crazy process, someone finally writes some code.  NOW we are getting somewhere.  Well, maybe not.  Code is also a form of written communication.  If we write agile communicationhard-to-understand or very complex code, we end up once again getting into a place where communication suffers.  We then create a lot of comments that will "explain" what we are trying to do.  At least at the moment we wrote the code.  Code changes though.  As we start working with the actual software, we see things we would like to either modify, or perhaps even fix.  Most of the time this happens in a hurry, so we change the code, and don't have the time to ensure the comments are updated as well.  In essence, we start to lie to future readers.  "This code does this, and it does it this way" only lasts until the first revision.

This all brings me to my main point about communication.  Once we've written all of our documents, argued over the formats, written the code, reviewed the code (now *there* is an area where you can really see arguments about format) and delivered the code, what are we really going to be discussing?  The *working software*.  We look at what it is doing.  We play with it.  We talk about how to make it better, faster, stronger. We don't go back to discuss the document ever again.

So let's spend less time worrying about the document.  In Extreme Programming, and of course in many of the other agile methodologies now, we talk about fitting a user story on an index card.  Any further elaboration comes best from writing software and talking about what we have.  Another great way of communicating our needs is to write automated acceptance tests.  We are identifying how the software is expected to work and we are unambiguously showing what we want.

So to circle back to where we began, communication is about shared understanding.  Whatever mechanism we find most useful, we should embrace.  We have found that the most succesful mechanism, without exception, is the spoken word.  If for whatever reason we find that to not be possible, maybe due to the distributed nature of some agile teams, we need to look for the best way to communicate and overcome the inherent difficulties in not being able to talk to each other directly.  The best way to communicate what the software should do is to provide automated acceptance tests.  And of course the best way to communicate what the software does is to create it and use it.

Leave a Reply

Your email address will not be published. Required fields are marked *

fourteen − three =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch