Interesting read. Very thought-provoking. Food for thought with different look at how information technology integrates with business needs and goals. The use of the novel as a teaching tool is a good idea. This book is definitely worth a read. ( )

Started reading .... but despite some interesting moments lost interest. Unfinished ( )

This one is rather interesting book.

On one hand it tries to show how inter-departmental cooperation, especially between IT services and between IT and actual business can prove highly valuable and can speed up and stream-line the main business processes and business-supportive projects/processes.

On the other hand for the dramatic purpose, issues that take significant amount of time in real life are shortened to a ridiculous short time-spans and some teams are shown as very slow-movers and not very capable. Some IT departments are shown as especially ... troublesome.

So I understand some of the reactions to the book (I recognized myself in several characters).

In my opinion what this book does very good is to show what exactly DevOps is - improvement in overall organizational thinking and planning, striving to achieve more in smaller steps [remember those many sayings like brick-by-brick-you-get-a-house]. If everyone is working together, if everyone is motivated and aims for the same - success of the core business - everything can be achieved.

All in all very interesting book that tries [in form of a fiction instead of academic or professional-literature way] to give insights to the readers how things can be much easier achieved through DevOps approach. And funny thing is that all the lections presented are applicable everywhere - not just to IT.

Recommended to everyone interested in organizational and planning issues. ( )

I dunno. It started out fun then became less fun. ( )

This was a real slog. The book leans heavily on stereotypes and cliches, and talks a lot about (awful) people's (awful) feelings, and needed a lot more editing. There are interesting ideas in there, but I think I would've been better off just reading the appendices (or maybe the DevOps Handbook, which is up next). ( )