Why is it so difficult to talk to customers? Why do managers often end up making unrealistic demands on developers and encouraging them to make promises that they can't keep? Why do so many software projects end up in angry exchanges of accusation and counter accusation? Can any of this be explained? Can anything be done to make it better?

Researchers at the "Harvard Negotiation Project" claim that a great deal can be done to make things better. By understanding the structure of "difficult conversations" we can be made aware of the various points at which things can go badly wrong and sometimes avoid them. By understanding our own contribution to the problem we can adopt strategies that give us a chance to actually improve a situation.

Using as examples a particularly "difficult" conversation about the development of a website that I overheard in a cafe, and my own experiences in developing software over the last 15 years, I'd like to explore how understanding the nature of "difficult conversations" and some other basic negotiation strategies can help anybody involved in the business of developing software.

Suitable for:
Suitable for anybody involved in the process of developing, managing or commissioning software.

	Xtend Sven Efftinge : 1st Feb 2012
	JSR Martijn Verburg : 1st Feb 2012
	Neo4j Internals Tobias Lindaaker : 25th Jan 2012
	HTML5 & Android Webview Dave Springgay : 19th Jan 2012
	ScalaMock Paul Butcher : 18th Jan 2012
	Real-world Clojure Malcolm Sparks : 17th Jan 2012
	1000 lines of Clojure Julian Birch : 17th Jan 2012
	paredit-mode Neale Swinnerton : 17th Jan 2012
	Clojure & MaxMSP Nick Rothwell : 17th Jan 2012
	Grails 2 Peter Ledbrook : 16th Jan 2012
	Enterprise Integration John T. Davies : 12th Dec 2011
	Spock Luke Daley : 8th Dec 2011
	Getting Groovy on the Web and Desktop Andres Almiray : 8th Dec 2011
	DiscoBot: Groovy on Android Erik Pragt : 8th Dec 2011
	KEYNOTE - Groovy Update Guillaume LaForge : 8th Dec 2011