Dialogue-driven development, what we are calling d3, is an evolving set of principles for developing software. It’s a desire to extend our understanding of and lend formalism to the collaboration value of the Agile Manifesto.
We definitely don’t believe that one size fits all. But we are opinionated about practices that lead to better software. We know that capturing correct, useful requirements is hard. We believe that simplifying the process is important. We want to explore how much we, as clients and developers, can accomplish by focusing on the quality of our interactions.
Dialogue-driven development is not a particular methodology like Scrum or XP. It intends to be, however, useful to any agile methodology. It aims to do more than just better facilitate the exchange of information at a superficial level. Rather, d3 should enable us to established shared meaning. The difference between hearing and understanding. We also believe dialogue is a transformative process. Developers and clients are not two chunks of granite that are brought into proximity and then depart. Interaction is a process of mutual influence that changes the participants.
Recent Articles
- Principles of d3: Simplicity, by Brian Ford
- Teams Need Healthy Collaboration, by Robby Russell
- Project Enlightenment with d3, by Robby Russell
- Of Dialogue and Development, by Brasten Sager
- Why we focus on solutions, not products, Brian Ford
- Patterns of Dialogue, by Brian Ford
- Dialogue-Driven Development, by Robby Russell
- Ethical Software Needs Dialogue, by Brian Ford
- It’s all about the dialogue, by Brian Ford
- d3 is about rounded corners, by Robby Russell
Interaction
We often see forums and communities creating inclusive groups. But who’s included?
We’re talking about collaboration here. We’d like to see everyone participating. That’s right. This isn’t about developers talking to one another about those clients over there. Our goal is getting developers and clients talking together about making better software.
