Those interested in some data metrics, scroll to the end of the post, after the quotes \ud83d\ude42<\/p>\n
What book did we read?<\/h2>\n
![\"\"](\"https:\/\/i.imgur.com\/YTKk46O.jpg\")
<\/p>\n
We read the book called The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win<\/a> by Gene Kim, Kevin Behr, and George Spafford. This is a book that, arguably, everyone in IT should read.<\/p>\n The book is really awesome, and here’s the Amazon rating<\/a>:<\/p>\n If you don’t trust Amazon for some reason, here’s the Goodreads rating<\/a>:<\/p>\n The rating score of We started reading the book on Jan 21st and finished it on Mar 11th. So, for 6 weeks we read approximately 50 pages per week and then discussed it in our mobile dev team meetings.<\/p>\n This is only 10 pages per workday, in case you were wondering. Here’s a short post on the math behind reading 30 books per year<\/a> in case you’re interested.<\/em><\/p>\n We learned that there are 4 types of work:<\/p>\n We learned some new phrases like FUBAR and MOADF, and we learned that everyone needs idle time<\/strong>, because if no one has idle\/slack time, WIP (work in process) gets stuck in the system just waiting.<\/p>\n Also, we learned that getting the whole company working together to the same common goals only works if people know what the goals are. So, it’s good to have OKRs\/KPIs\/yourVersionOfGoalTracking publicly available and set by each department and their team members.<\/p>\n The book also spurred some exciting discussions about:<\/p>\n There were some things that we didn’t like:<\/p>\n Speaking of characters, it seems like we all liked the Eric character, which could be described as a mix of Doc and Jack Sparrow. That also knows a lot about process and IT and also surfs not only the internet.<\/p>\n Since every good novel has to have a villain, this one did as well. We liked the fact that Sarah got what was coming for her in the end. And we even toyed with an idea of who would play this character in the \u201cThe Phoenix Project\u201d movie. Here are a few options that were mentioned:<\/p>\n As usual in my book posts, here are some quotes that we liked:<\/p>\n So, it does seem that we liked it and had fun, but how do you measure that?<\/p>\n This is how much we liked the book on a scale from 1-10:<\/p>\n Funny piece of trivia was that iOS devs used floats, and Android devs used integers. ?<\/p>\n This is how much we liked the book club implementation on a scale from 1-10:<\/p>\n And, finally, this is how likely we want to do this again in Q2 on a scale from 1-10:<\/p>\n I promise I didn\u2019t set this graph up on purpose to look like this, but it does look kinda cool.<\/em> ?<\/p>\n We liked this experiment and will continue doing it. I hope you found it valuable and that you also may wanna try out this within your teams. If you have any questions, please ask in the comments section.<\/p>\n And, a question for those that already conducted book clubs in your engineering organizations, what books did you read?<\/p>\n How we implemented the #book<\/a> #club<\/a> idea in our #engineering<\/a> team https:\/\/t.co\/lLQ5LuVUw6<\/a><\/p>\n — Nikola Bre\u017enjak (@HitmanHR) March 25, 2019<\/a><\/p><\/blockquote>\n![\"\"](\"https:\/\/i.imgur.com\/eOL1RmK.jpg\")
<\/p>\n![\"\"](\"https:\/\/i.imgur.com\/YT8aTA9.jpg\")
<\/p>\n4.25 out of 5<\/code> from almost 19k votes is a lot on Goodreads.<\/p>\nHow did we do it?<\/h2>\n
What did we learn?<\/h2>\n
\n
What discussions did the book start<\/h2>\n
\n
What we didn’t quite like<\/h2>\n
\n
\n
Characters<\/h2>\n
![\"\"](\"https:\/\/i.imgur.com\/zHdLoZD.jpg\")
<\/p>\n![\"\"](\"https:\/\/i.imgur.com\/gdArJaD.jpg\")
<\/p>\nSome quotes<\/h2>\n
\n
Show me the data!<\/h1>\n
![\"\"](\"https:\/\/i.imgur.com\/UUqUkiJ.jpg\")
<\/p>\n![\"\"](\"https:\/\/i.imgur.com\/rRz7fRx.jpg\")
<\/p>\n![\"\"](\"https:\/\/i.imgur.com\/JjsqsJL.jpg\")
<\/p>\nConclusion<\/h1>\n
\n