How can development organizations ensure building reliable systems, yet responsive to change? This is a fundamental question plaguing Agile organizations. The key is collaboration. Mark Hammer explores process changes and tools your organization can use to ensure high quality software, while maintaining the flexibility to respond to change. He highlights examples from large and small companies showing how simple changes can improve team performance, increase employee satisfaction and save the company money in expensive software fixes.

 The session highlights several key findings:

 1. PROCESS. Best practices for collaboration, focusing on what a collaborative culture looks like. How can managers foster collaboration? How can developers, testers and product managers work together to solve problems previously managed by just one of these groups?

2. TOOLS. What tools can foster collaboration across these teams? And how can these tools be used to help teams adapt to new customer findings? I review several categories of collaboration tools, with special emphasis on tools that have impacted the ability of specific companies to collaborate and improve quality metrics and results.

3. MEASUREMENT. Ways other companies have tried to measure collaboration and its impact on team performance, highlighting specific examples including companies that have put in place process and tools then measured their ROI against them.