That part is really useful. Give me some more of that. Oh, that's hard. And so on, and so on. Lengthy development phases dominated by one party or the other are like a conversation partner who declaims without listening.
Healthy conversation goes back and forth, back and forth.
Conversational projects never go more than a week or two without giving both parties a chance to talk. Valuable conversations take place between peers. Neither dictates the agenda. In conversational development, this takes the form of business people making business decisions, such as scope, priority, and dates, and technical people making technical decisions, such as estimates. Conversational software development encourages and relies on both parties learning and applying new ideas during the project.