Luke Hohmann

A few years ago, I was helping with a large-scale enterprise Agile Transformation project led by Applied Frameworks. The client had several hundred engineers spread across multiple locations, and was a cloud-based infrastructure company that has grown very rapidly both organically and through multiple acquisitions. A key part of Applied Framework's transformation services is starting every transformation with retrospectives so that we can better understand what all members of the product development function - from developers 

and quality assurance, to product management and customer care - think about what is going well and what needs to be improved.

Speed Boat is our game of choice for retrospectives. But the size of the organization involved meant that we would be conducting multiple moderately large retrospectives of 30 to 40 people. This was costly, of course, and time-consuming, but the enlightened leadership of this company was committed to understanding the perspective of their employees before cramming Agile down their throats.

Webinar: Why You Need Enterprise-wide Retrospectives

July 17, 2014 | 11:00 AM PDT

As organizations widen their use of Agile, Agile's core team-based practices can begin to be stretched. In those situations, we need to re-think and adapt them to fit the wider

Luke Hohman

context. Retrospectives, for example: While they can help individual teams improve, these events can become isolated and fail to address the needs of the organization, issues that are beyond the control of a single team. That's where collaborative, social serious games come in.

Register today and join us on Thursday July 17, to learn how you can use Innovation Games to create enterprise-wide retrospectives.