Do the developers fight a guerrila war against the sales people? Does the sales process exists in a galaxy far far away from the development process? Are client managers the great disempowered middle child? The resented controller? Do engineers/developers take responsibility for client satisfaction and improving the bottom line? Without force?

Does one person play all three roles? (This session will help you too!) Where does design and strategy fit in? Bonus question: Does anybody, anywhere, know how to estimate?

In this session, we'll explore proven ways to integrate the three aspects of development -- client acquisition, project/client management, and application development -- into one big group hug. We'll explore:

• Scrumming it up: using the scrum process to push all issues towards the person who can resolve them.
• Mutual empowerment: Define common languages and tools that convey necessary information. For example, "Don't geek at me when it's not necessary." and "Don't bottom line me when I'm working over here."
• Sandler as a common tone: Set the tone for *all* client interaction from first handshake to final goodbye to match the sales process.
• Expectations: Ensure that expectations are being set by the people who will meet them. Create systems to ensure that everyone understand what is expected of them and has a voice in the process. (Hint: this is where estimating will come in.)
• The bottom line: An empowered team is a profitable team, so share the responsibility for financial success appropriately.
• Management team meetings: Ideas for tools and strategies that create cohesion.
• Client manager as host: If Drupal development is a party, the client manager is the host. How do you ensure they throw the best parties in DrupalLand?