Here at Skybox Labs, we do regular lunch and learn session where a fellow colleague present on topics ranging from clean code, continuous integration, game development, machine learning to almost any areas where there are reasonable interests.
One of the very recent lunch and learn series that I have attended was focusing on DevOps which got me interested to learn more about the topic. I was looking for recommended books and the lead presenter highly recommended that I start with 'The Phoenix Project' by Gene Kim
Being inspired by the stellar reviews in Amazon, I have decided to get a copy and read it over the weekend.
A fantastic book that contains a wealth of information and delivers it in an intelligent and interesting way; a story. The book successfully captures the events and struggles of most people who work in IT Operations and gives a very good explanation on why these problems exist, and how you can solve them. It portrays a very effective way of thinking in applying our understanding of plant floor operations, manufacturing, and logistics to how we manage IT in a business. The way it establishes that connection is fantastic.
Beside throughly enjoying the book as a breathtaking novel, here are my few key takeaways from this book:
- Definitely a must read for anyone in leadership position. The vivid narrative presented in this book should convince anyone about the importance of well run IT in overall business success.
- Know and master The Three ways.
- Work is not done until it is in the hand of your end users/customers. Every team is equally responsible and should work together to make that happen. It is not like DEV team is done now it's QA's job.
- The more we can automate the hand-off between teams the less chance of failure and unplanned work. For example, crux of the deployment issues phoenix team initially faced was due to the fact that their DEV, QA and PROD environment were not on sync. After they automated the environment creation and made it consistent across DEV, QA and PROD that problem resolves itself. Also, now they could spin a new DEV machine in record time as a nice side effect. This eventually points to the importance of continuous integration, deployment and a tight feedback loop to make the pipeline more robust.
- Frequent deployment immensely helps business to experiment on the market need, iterate quickly on the winning features and retire the ones which are not as successful. Also it gives the development team more confidence on their process as it gets easier to push bug fixes or roll out new features.
- It is immensely important to have a clear understanding of core business goals, each team's roles on achieving those goals and relating those goals to relevant work items.
- Understand Four types of work and their differences.
- (a) Business project (Delivers customer value) - New Solar powered Car - Halo Infinite
- (b) Internal IT project (Production line for delivering (a)) - Paint machine, Crash tester - Source control, Automated test, Continuous delivery
- (c) Changes(improve (a) and (b)) - Replacing Faulty car parts, Reduce production time - Usual Bug and hot fixes and performance tuning
- (d) Unplanned work (Basically paralyze all the other works) - Painting machine broken down so cars in the assembly need to wait until it is fixed - Build broken.
- My favorite character - Erik, hated character - Sarah. However, both were equally important to create the necessary tension in the story.