The Phoenix Project DevOps simulation

Lessons from the DevOps Simulation “The Phoenix Project”: Continuous Learning

At Solidify, we offer an interactive DevOps simulation named after the famous book The Phoenix Project by author Gene Kim. The simulation targets why DevOps is so important as well as what behavior and processes are needed in order to increase team efficiency. The simulation game is developed by GamingWorks and their co-owner Jan Schilt. Below are some outlined lessons on continuous learning that the team hopefully discovers themselves during the simulation.

Original post by Jan Schilt can be found here.

A Definition of Continuous Learning

I like this definition of Valerie I. Sessa in her book: From Continuous Learning, individual, group, and organizational perspectives:

Continuous learning at the team level is a deepening and broadening of the group’s capabilities in (re)structurering to meet changing conditions, adding new skills and knowledge and (re)creating into a more and more sophisticated system through reflection on actions and consequences.

Lesson 1 – Plan Time for Learning

 

Do, reflect, think, decide

Learning is a process of doing, reflecting, thinking and deciding. Each of the steps are important. The doing is your day to day work, which takes mostly all of your 40 hours week. We hardly take time for reflection, thinking and making decisions what we are going to do different. Maybe we stop a bit to long in front of a traffic light because we are reflecting. Maybe you do not hear your children during diner while they are telling stories about school, because your a thinking about a new way of working.

In the worst case you are not doing this at all and simply take a decision to ‘try’ something else. But, this is not the learning that will make a team grow. Learning should be an organized process with the team using the learning cycle of Kolb.

Lesson 2 – Learning in Teams

Lessons learned from the phoenix project simulation

Since we are working in teams, we should learn in teams as well. It’s best to assign a ‘facilitator role’ to one of the team members. This role can manage time, observe the learning process and can give feedback to the team if they move to fast or if not all team members are involved.

Learning in teams also mean we need to learn to give feedback to each other in a constructive way with a focus on making the team a better team. It’s not about finding out ‘who was making the mistake’, it’s about avoiding them the next time. We also have to create a safe and open environment in which we are free to talk and explore.

Lesson 3 – We have to think before we decide!

Finding solutions is very important in solving problems. For this we need to have a clear picture of the problem we want to solve (output of Reflection). Then the creative part starts; thinking. During this proces we are building a solution as a team. We draw, we discuss, we try to test solutions, we combine ideas and we build a solution. This process is crucial for the team result. This gives all team members the feeling that they are part of making their own work better. The outcome does not to be sold to the team, we don’t need to create buy-in. It’s the result of the team. We even create real ownership from the team, which make next improvements easier to organize since ‘it’s our solution’. 

After this ‘Thinking’ it’s not a big step for the team to ‘decide’ what we are going to do with the solution. The team will be eager to apply the new solution in the day to day work. It’s their solutions by the way, something to be proud of.

Lesson 4 – We need to ‘measure’

It’s always good to measure if the decision of the team was the one that created impact. We have to check the results. Did we went faster? Did we work better? Are we all happy with the outcome? These questions should be the starting question of the next learning cycle (reflection). Don’t forget to evaluate the learning process it’s self by asking a question as: “How did the learning process work?

And, celebrate the results as a team! Be proud of the results.

Lesson 5 – Share Knowledge

Lessons learned from the phoenix project simulation

This is something which is easy to forget. We need to realize we are working as a team within an organization. Maybe other teams will have the same kind of questions or problems? Why do we let them reinvent the wheel? 

Think about ways of sharing. Use social media. Join learning (retrospective) sessions from other teams. 

 

Have your team started working with DevOps? Have you read The Phoenix Project and found inspiration? Let us know in the comments below!

Leave a Reply

Your email address will not be published.