This post originated from an RSS feed registered with Agile Buzz
by Robby Russell.
Original Post: Announcing the Dialogue-Driven Development Project
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
But d3 is an evolving thing. Its earliest forms offered very little definition, leading me to believe there was little to it. As it has evolved the goals and mindset of d3 and its proponents have become a little more clear, and after further consideration I���m now convinced that my original critiques may have been wrong.
I encourage you to read his article, which offers ideas (and diagrams) on how d3 might be injected into your existing process.
A small number of interested developers have been sending us questions about d3 and were wondering what the next step was for the community. We’re working hard on outlining patterns of dialogue, which is where we plan to put of our focus into. A small group of people have joined our mailing list and IRC channel over the past few weeks, where some conversations have occurred. After reading through Brasten’s post, I believe that our IRC conversation last week was a good example of how people with different ideas about something… can come together and have a shared understanding, which is exactly what Dialogue-Driven Development is about.
Through shared understanding, we can accomplish so much more.
“In true dialogue, both sides are willing to change.” ���Thich Nhat Hanh
Thanks to the hard work of Brian Ford, we now have a website to announce, which will be the portal to various conversations, patterns, and resources related to Dialogue-Driven Development.
Previous Topic
