Hello! I`m want to start my blogging from the reflection of the books that had big influence on my vision of IT technologies. For people who`s already read this books this article may be interesting to synchronize our vision and terminology. For people who`s not read this book, post can help to decide if they want to read it or not. I`ll try to write only my thoughts and reflections and use minimum spoilers to peoples who`s not read this book yet. Ok, let`s go! The book is THE PHOENIX PROJECT written by Kevin Behr, George Spafford and Gene Kim. As authors says: A Novel About IT, DevOps, And Helping Your Business Win.
This book can be an introduction to DevOps methodology in company and must be read by all employers. Main idea of the book, as I think, is worth that IT department can bring to business when they understand KPI (Key Point Indicators) of other departments. That obvious keynote is very often misunderstood by both: IT Department and other departments, and leads to inefficiency and wasting of resources. The keynote concerns to lean methodology and describes why or what-for or results of implementing new methodologies. Second keynote concerns directly to DevOps techniques. It says that reduction in release time allows IT department to be more flexible and accurately correspond the needs. How do you think is small release every day with one actual feature better than big release once in half-year with a big amount of changes some of that already deprecated? This keynote concerns directly to IT departments. And the third keynote shows generic problems in IT department and ways to answer them.
The book is written as a novel and has a small amount of IT terminology. That`s why as I think it can be interesting for a wide range of public and as I wrote before must be read in companies that decide to implement this principles. Three keynotes described in this post is only IMHO and if you also read this book and see other keynotes please feel free to discuss this in comments. Upvotes also are welcome.
