Yesterday we ran a public version of The Phoenix Project Game to give a bunch of people a feel for how it works and the kind of outcomes they could expect when they run the game with their own teams. If you missed this one but it sounds like something you want to do, we have another one in October; you can register yourself on it here but be warned - the last one booked out super-quick!Read More
Ranger4 DevOps Blog
I recently had an opportunity to observe the Phoenix Project Game in action at UCAS headquarters in Cheltenham. Here's what I saw!
During the Introduction I learned:
- A few players had heard of this thing we call DevOps and read The Phoenix Project book - neither is a pre-requisite to playing the game although it's useful to have a few in the room with awareness of the DevOps principles - that is what we are here to learn though!
- Many of the players played their own roles in the game - some customers like to do this, some like to mix it up I have noticed. I guess playing a role that isn't your own is an opportunity to build more understanding and empathy for the challenges our colleagues face, but the advantage of playing your own is to be able to directly apply learnings to your everyday life. I don't think it's possible to switch roles during the game though - I think that would inhibit the flow of learning.
In the First Round
At the start of the first round, the CEO (the Game Leader, in this case, Helen) sets the high level business goals for the game - there are two:
- Revenue target - $110,000
- Share price - $23.00
Teamwork was visible from the start with Application Development's and Change Management's curiosity in what other players had at their disposal. A clear hierarchy was demonstrated with Retail Operations, the CFO and Human Resources taking turns in leading group discussions. It was also good to see players discuss the round's business objectives and current live issues around VP of IT Operations & CISO tables.
I recently had the opportunity to act as an observer during a Phoenix Project Game at the Headquarters of The Royal Society for the Protection of Birds (RSPB) in Sandy. I've wanted to observe a Phoenix Project Game (TPP) for a while now and this was a the perfect opportunity to do so. On top of that, I got to see Sandy's beautiful surroundings.Read More
On Monday this week we ran another The Phoenix Project Game Taster session in London. We did a half day session this time in order to make it easier for people to take time out of their day and had twelve attendees (perfect!) from a variety of banks, insurance companies, building societies and charities. It was in some ways a slightly nerve-wracking approach in that the danger was that we would only be able to run two of the four rounds of the game so people would leave at the point where they reach the 'slough of despond' having not played all the way through to the end where all the dots are connected and all of the loops closed. I'm pleased to report that it wasn't a disaster by any means and people understood plenty about where the game was going in order to be able to imagine what would happen next and were happy about being able to get back to their desks in the afternoon.Read More
And we’re live! The Phoenix Project Game is a go! For those of you who are part of the DevOps movement or are looking into DevOps as a way to improve your business, The Phoenix Project (TPP) is a must read. Unlike most other IT process books, TPP is written as a novel and revolves around the protagonist and newly promoted VP of IT Operations, Bill. The company, ‘Parts Unlimited’, is at an all time low; stock has tumbled and they now trail the competition in sales growth, inventory turns and profitability. Behind closed doors however, Parts Unlimited has invested heavily in its secret weapon: “The Phoenix Project”, which has long promised to close the gap on competition by combining new, cutting edge technology with existing practices. However, not all goes to plan and the company is on the brink of disaster.
In short, Bill ends up meeting the business version of Yoda, who inevitably shows him the ways of the force, or in DevOps terms “The Three Ways”. As Bill progresses on his journey of discovery, he starts to combine the practices of Agile, Lean and ITIL, and slowly but surely, manages to save the business!Read More