The Artima Developer Community
Sponsored Link

Agile Buzz Forum
The Technology of Dialogue

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Robby Russell

Posts: 981
Nickname: matchboy
Registered: Apr, 2005

Robby Russell is the Founder & Executive Director PLANET ARGON, a Ruby on Rails development firm
The Technology of Dialogue Posted: Sep 12, 2006 1:52 PM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by Robby Russell.
Original Post: The Technology of Dialogue
Feed Title: Robby Russell gets agile
Feed URL: http://www.robbyonrails.com/xml/rss20/tag/agile/feed.xml
Feed Description: Robby on Rails gets agile with Dialogue-Driven Development
Latest Agile Buzz Posts
Latest Agile Buzz Posts by Robby Russell
Latest Posts From Robby Russell gets agile

Advertisement

In the essay, Dialogue and Organizational Transformation, Glenna Gerard and Linda Teurfs outline the the building blocks of THE TECHNOLOGY OF DIALOGUE, which they suggests consists of:

  • Suspension of Judgment
  • Identification of Assumptions
  • Listening
  • Inquiry and Reflection

What makes dialogue different than conversation? According to David Gurteen, “dialogue is a disciplined form of conversation.”

Gurteen says that within dialogue1:

  • You prefer a certain position but do not cling to it.
  • You are ready to listen to others.
  • Your mindset is not one of ‘convincing others that your way is right’ but of asking what you can learn from them.
  • It is recognizing that other people���s input will help you refine your own ideas or reveal your misconceptions.
  • It is not argument or debate. It is not win-lose. In dialogue all sides win by coming up with a more appropriate solution than a single person could ever have. It is win-win.

When we first introduced Dialogue-Driven Development, Ryan Allen responded with a brief overview of how you might go about defining a failed project. His first bullet was, “Miscommunication can lead to the implementation of the wrong solutions.”

It is our opinion that many of the problems that lead to failed projects can be solved through consistent and cooperative discourse. Much of this relies on each of us taking ownership of our commitment to encouraging healthy collaboration between developers, clients, and users.

Wikipedia currently describes dialogue as, “a reciprocal conversation between two or more persons.”

Question

What are some of the obstacles that you face when interacting with a diverse set of developers, clients, and users?

1 The Discipline of Dialogue by David Gurteen

Read: The Technology of Dialogue

Topic: carnival of the agilists, 7-sep-06 Previous Topic   Next Topic Topic: Loops and OO and Parallelism

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use