You hear it a lot: DevOps is not just about tools, but also about changing company culture. But just how does an organization firmly rooted in traditional software development go about making that change? This in-depth report shows how two large organizations, Nordstrom and Texas.gov, moved from long-established software development models to the collaborative style DevOps embodies.

Based on a series of interviews he conducted with key team members at each organization, release engineering consultant J. Paul Reed describes the process they went through—from initial responses to critical, game-changing events through the trial and error of deciding how DevOps would work for them. As you’ll learn, the process included its share of false starts, in not only the way teams were structured but also the path that code took from commit to customer.