Why the Phoenix Project?
Business is demanding ever shorter release cycles for new applications. Traditionally “Operations” is seen as a barrier with lengthy bureaucratic controls and delays in deployment, and “Development” as throwing solutions over the wall.
DevOps is not a framework or method. It is an approach, a philosophy based on principles. Applying these requires a new mindset, new behaviors and a cultural change in both Development and Operations. They must now work closely together.
Typical learning objectives of the The Phoenix Project are:
- Apply DevOps principles in a real life situation.
- Find the right balance between delivering on SLA requirements and IT projects according to plan.
- Experience how DevOps can bring serious value to the business.
- Increase the efficiency and effectiveness of the IT Department.
- Show business their responsibility for successful IT projects.
The simulation is based on the book The Phoenix Project. This project represents an IT enabled business transformation, with Retail Operations as the business owner of the project.
Participants act in different business and IT roles within the Parts Unlimited organization. The team´s challenge is to use the DevOps principles and apply them to ensure the survival of Parts Unlimited.
In 3 rounds the team works on the IT projects and issues to ensure that The Phoenix Project will be finished on time. But, meanwhile the business keeps coming with new ideas and demands, and external developments beyond the team´s control also frustrate the progress of the project.
Number of participants: 8 – 12
Expertise: no specific requirements