Robby on Rails: DDD (d3) is the new conversational software developmentthoughts.sort_by{|t| t[:topic]}.collect tag:www.robbyonrails.com,2005:TypoTypo2006-09-05T22:12:48-04:00Robby Russellurn:uuid:c793b3bf-28f5-4a13-b03f-2d069e96bc0e2006-08-03T22:28:00-04:002006-09-05T22:12:48-04:00DDD (d3) is the new conversational software development<p>I’m not sure how I missed this recent post on Martin Fowler’s bliki last week on <a href="http://martinfowler.com/bliki/CustomerAffinity.html">Customer Affinity</a>. In this post he references when the term “agile” first came about and mentioned that, “one of Kent’s suggested names for ‘Agile’ was conversational software development – the point being that it’s a two way communication. “</p>
<p><em>Conversational</em> Software Development.</p>
<p>This doesn’t sound so different than what Brian Ford and I are calling, <a href="http://c2.com/cgi/wiki?DialogueDrivenDevelopment">Dialogue-Driven Development</a>. ;-)</p>
<p>Fowler goes on to say, <em>“This isn’t something like a telecoms protocol that you can define, but the back and forth discussions about how software can enhance the business are where the real value lives. Much of this conversation is of half-baked ideas, some of which grow into valuable features – often ones that aren’t things that the customer originally thought of.”</em></p>
<p>If you didn’t follow the thread of comments on my <a href="http://c2.com/cgi/wiki?DialogueDrivenDevelopment">recent post on Dialogue-Driven Development</a>, you might not know that this name came up during Martin Fowler’s keynote at RailsConf when Brian and I were sitting next to each other and Martin kept reusing the word “dialogue.” Brian and I can’t seem to agree if I said, “Dialogue-Driven Development” out loud or if he wrote it down on a piece of paper first… so we’re going to have to share the credit. What made this so fascinating at the time was that for the entire trip from Portland to Chicago on the <a href="http://www.theargonexpress.com">Argon Express</a>, Brian and I had been discussing a lot of what we’re planning to change and define with our approach to Client/Project/Development Collaboration & Management… and in the end… we left Chicago with <del><span class="caps">DDD</span></del> d3.</p>
<p>Thank you, Martin for being part of this process.</p>
<p>Like all things, this approach is open to <del>discussion</del> dialogue.</p>
<p><strong><span class="caps">UPDATE</span></strong></p>
<p>Brian has written an article called, <a href="http://blog.brightredglow.com/articles/2006/08/04/its-all-about-the-dialogue">It’s all about the dialogue</a>. (<a href="http://digg.com/programming/It_s_all_about_the_dialogue">digg.it</a>)</p><p>I’m not sure how I missed this recent post on Martin Fowler’s bliki last week on <a href="http://martinfowler.com/bliki/CustomerAffinity.html">Customer Affinity</a>. In this post he references when the term “agile” first came about and mentioned that, “one of Kent’s suggested names for ‘Agile’ was conversational software development – the point being that it’s a two way communication. “</p>
<p><em>Conversational</em> Software Development.</p>
<p>This doesn’t sound so different than what Brian Ford and I are calling, <a href="http://c2.com/cgi/wiki?DialogueDrivenDevelopment">Dialogue-Driven Development</a>. ;-)</p>
<p>Fowler goes on to say, <em>“This isn’t something like a telecoms protocol that you can define, but the back and forth discussions about how software can enhance the business are where the real value lives. Much of this conversation is of half-baked ideas, some of which grow into valuable features – often ones that aren’t things that the customer originally thought of.”</em></p>
<p>If you didn’t follow the thread of comments on my <a href="http://c2.com/cgi/wiki?DialogueDrivenDevelopment">recent post on Dialogue-Driven Development</a>, you might not know that this name came up during Martin Fowler’s keynote at RailsConf when Brian and I were sitting next to each other and Martin kept reusing the word “dialogue.” Brian and I can’t seem to agree if I said, “Dialogue-Driven Development” out loud or if he wrote it down on a piece of paper first… so we’re going to have to share the credit. What made this so fascinating at the time was that for the entire trip from Portland to Chicago on the <a href="http://www.theargonexpress.com">Argon Express</a>, Brian and I had been discussing a lot of what we’re planning to change and define with our approach to Client/Project/Development Collaboration & Management… and in the end… we left Chicago with <del><span class="caps">DDD</span></del> d3.</p>
<p>Thank you, Martin for being part of this process.</p>
<p>Like all things, this approach is open to <del>discussion</del> dialogue.</p>
<p><strong><span class="caps">UPDATE</span></strong></p>
<p>Brian has written an article called, <a href="http://blog.brightredglow.com/articles/2006/08/04/its-all-about-the-dialogue">It’s all about the dialogue</a>. (<a href="http://digg.com/programming/It_s_all_about_the_dialogue">digg.it</a>)</p>