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.

	Introducing Neo4j Toby O'Rourke : 23rd May 2012
	JavaScript with Gradle Luke Daley : 22nd May 2012
	Perfect Clojure John Stevenson : 16th May 2012
	MongoDB with Grails Chris Harris : 16th May 2012
	Non-rails Groovy development Sean Reilly : 16th May 2012
	CouchDB at the Hut Group Tom McMillen : 9th May 2012
	The Couchbase Server Tutorial John Zablocki : 9th May 2012
	Neo4j Tales from the Trenches Nicki Watt : 9th May 2012
	Is Everything Social? Gavin Bell : 8th May 2012
	Neo4j Intro Ian Robinson : 3rd May 2012
	Polyglot apps in Java and Spring Jan Machacek : 3rd May 2012
	Parkbench Various Speakers : 3rd May 2012
	Moving Beyond Objects Brian Sletten : 3rd May 2012
	Exploring enterprise Java David Morgantini : 3rd May 2012
	Connecting to Neo4j using Spring Data Anirvan Chakraborty : 3rd May 2012