Robby on Rails: Teams Need Healthy Collaborationthoughts.sort_by{|t| t[:topic]}.collect tag:www.robbyonrails.com,2005:TypoTypo2006-10-18T10:11:42-04:00Robby Russellurn:uuid:6b56d77b-4bec-4d2f-97eb-606e614ee6fe2006-10-18T10:05:00-04:002006-10-18T10:11:42-04:00Teams Need Healthy Collaboration<p>A few weeks ago, I was explaining some of the concepts behind <a href="http://www.dialogue-driven.org/">Dialogue-Driven Development</a> to <a href="http://www.michaelbuffington.com/">Michael Buffington</a> and when I said that we were working to create <a href="http://blog.brightredglow.com/2006/08/22/patterns-of-dialogue">patterns of Dialogue</a>... his immediate thoughts were on code. I don’t remember the exactly how he worded it.. but he basically thought we were working on a parsing tool for grabbing requirements out of emails, messages, etc. I quickly explained that d3 had nothing to do with actual code and was merely a practice that we as developers and consultants are using to think about our interaction with clients, users, and amongst ourselves.</p>
<p>Just last night, I was chatting with a friend of mine about d3… (names changed to protect the guilty)</p>
<p><strong>context:</strong> Harry works in a development team<sup><a href="#fn1">1</a></sup> of about ten people and Paul is one of his “team”mates.</p>
<pre><code>
Harry: i guess it prevents discussion domination
me: yeah, that happens as it is sometimes
Harry: and ensures equal contribution
Harry: paul does that
and he's not very polite about it either
and will often raise his voice and speak over you
which is crazy
kindergarten stuff
me: hah
Harry: need a talking stick!
</code></pre>
<p>This happens all too often amongst ourselves. While we’re striving to improve our client interaction… we often overlook our own internal struggles to <strong>achieve healthy collaboration</strong>. It takes discipline by every individual in a collaborative environment to really <a href="http://www.powells.com/biblio/0385479999?&PID=30561">think together</a>.</p>
<p>So, how does d3 address this? Well, it’s our goal that through mindful dialogue, we can cultivate healthier collaboration in all of our professional (and personal) relationships.</p>
<p>I would also like to point out a few common misconceptions about d3.</p>
<ul>
<li>d3 is not a methodology… <a href="http://groups.yahoo.com/group/scrumdevelopment/message/15257">nor a replacement for Scrum</a> or XP. d3 is a thoughtful practice that focuses on the collaboration between a group of individuals, whether they be clients, developers, managers, or users.</li>
<li>d3 is not a <a href="http://www.informit.com/articles/article.asp?p=25913&seqNum=6&rl=1">Silver Bullet</a>, but it can be used as <a href="http://blog.brightredglow.com/2006/8/29/tracer-bullets-are-about-aiming-not-firing">effective ammunition</a>.</li>
<li>d3 is not something <a href="http://www.amazon.com/Teach-Yourself-Extreme-Programming-Hours/dp/0672324415">you learn in a weekend</a>, but you might be able to find a <a href="http://www.powells.com/biblio/62-0415149118-1">good book on Dialogue</a> and have a new perspective on how you communicate with others.</li>
</ul>
<p>Dialogue-Driven Development is about being in the conversation as it is happening… and really listening.</p>
<p>The next time that you’re getting ready to interact with your teammates, ask yourself:</p>
<ul>
<li>Am I contributing something meaningful?</li>
<li>Am I listening to others well?</li>
<li>Is everybody contributing an equal share of information?</li>
</ul>
<p>If you’re quiet, try to speak up more. If you talk too much, be mindful of how much you may dominate a conversation. If you’re not participating at all.. why are you there?</p>
<p id="fn1"><sup>1</sup> You’ll be happy to know that Harry also gave his two-weeks notice yesterday.</p><p>A few weeks ago, I was explaining some of the concepts behind <a href="http://www.dialogue-driven.org/">Dialogue-Driven Development</a> to <a href="http://www.michaelbuffington.com/">Michael Buffington</a> and when I said that we were working to create <a href="http://blog.brightredglow.com/2006/08/22/patterns-of-dialogue">patterns of Dialogue</a>... his immediate thoughts were on code. I don’t remember the exactly how he worded it.. but he basically thought we were working on a parsing tool for grabbing requirements out of emails, messages, etc. I quickly explained that d3 had nothing to do with actual code and was merely a practice that we as developers and consultants are using to think about our interaction with clients, users, and amongst ourselves.</p>
<p>Just last night, I was chatting with a friend of mine about d3… (names changed to protect the guilty)</p>
<p><strong>context:</strong> Harry works in a development team<sup><a href="#fn1">1</a></sup> of about ten people and Paul is one of his “team”mates.</p>
<pre><code>
Harry: i guess it prevents discussion domination
me: yeah, that happens as it is sometimes
Harry: and ensures equal contribution
Harry: paul does that
and he's not very polite about it either
and will often raise his voice and speak over you
which is crazy
kindergarten stuff
me: hah
Harry: need a talking stick!
</code></pre>
<p>This happens all too often amongst ourselves. While we’re striving to improve our client interaction… we often overlook our own internal struggles to <strong>achieve healthy collaboration</strong>. It takes discipline by every individual in a collaborative environment to really <a href="http://www.powells.com/biblio/0385479999?&PID=30561">think together</a>.</p>
<p>So, how does d3 address this? Well, it’s our goal that through mindful dialogue, we can cultivate healthier collaboration in all of our professional (and personal) relationships.</p>
<p>I would also like to point out a few common misconceptions about d3.</p>
<ul>
<li>d3 is not a methodology… <a href="http://groups.yahoo.com/group/scrumdevelopment/message/15257">nor a replacement for Scrum</a> or XP. d3 is a thoughtful practice that focuses on the collaboration between a group of individuals, whether they be clients, developers, managers, or users.</li>
<li>d3 is not a <a href="http://www.informit.com/articles/article.asp?p=25913&seqNum=6&rl=1">Silver Bullet</a>, but it can be used as <a href="http://blog.brightredglow.com/2006/8/29/tracer-bullets-are-about-aiming-not-firing">effective ammunition</a>.</li>
<li>d3 is not something <a href="http://www.amazon.com/Teach-Yourself-Extreme-Programming-Hours/dp/0672324415">you learn in a weekend</a>, but you might be able to find a <a href="http://www.powells.com/biblio/62-0415149118-1">good book on Dialogue</a> and have a new perspective on how you communicate with others.</li>
</ul>
<p>Dialogue-Driven Development is about being in the conversation as it is happening… and really listening.</p>
<p>The next time that you’re getting ready to interact with your teammates, ask yourself:</p>
<ul>
<li>Am I contributing something meaningful?</li>
<li>Am I listening to others well?</li>
<li>Is everybody contributing an equal share of information?</li>
</ul>
<p>If you’re quiet, try to speak up more. If you talk too much, be mindful of how much you may dominate a conversation. If you’re not participating at all.. why are you there?</p>
<p id="fn1"><sup>1</sup> You’ll be happy to know that Harry also gave his two-weeks notice yesterday.</p>