To calculate the overall star rating and percentage breakdown by star, we do not use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyses reviews to verify trustworthiness.
This is a must read book for any software manager. Mik talks about his epiphany moments on his journey to creating the Flow Framework. My epiphany came while reading this book when I realised how poorly we currently manage software delivery. Mik talks about us being in the Installation Period (the early days) of the Age of Software. I might call it something different - the amateur period. Software managers today are mostly just amateurs doing the best we can based on our own experiences. We do not have the information that would truly allow us to manage in a professional manner.
Kim's Flow Framework is designed to address this issue. Unfortunately, this is where the book's one most massive flaw hits. He spends 8 out of the 9 chapters explaining why we need a flow framework in a beautifully clear manner. Unfortunately the 9th, and most critical chapter, that is meant to explain the Flow Framework is a rushed and unclear explanation.
I must start by saying there is a lot of solid information in this book. The author does a fantastic job of explaining some of the challenges that come along with organisations that have a project focus.
However, the book does a very good job of keeping you in suspense for "the framework" (Chapter 9), but much like Game of Thrones, the ending is very disappointing. The explanation is vague and the diagrams lack detail. I wasn't happy about this and I wanted more..... only to find all internet searches leading to the same place; Tasktops marketing page (the author's company).
So, if like me, you want a thorough example of the flow framework, sorry but you won't find it here.
This is really a discussion on how to do Enterprise Architecture for an isolated "slice" of a business, rather than the more traditional (and much-maligned) big-bang approach (specifically software product development, although many of the principles could be applied to other functions/fields too). There are some good insights here, and it did get me thinking about how to approach parts of this problem where I work, but towards the end of the book i was left wondering where the "how to" section was: practical guidance on how to actually execute the ideas seems to have been left out of the book. Still an interesting read, though.
some great stories to tell and concepts here, but you need to filter it with, 'this guy has a tool he wants to sell you to do this stuff'. however if you filter that and think about the concepts it's pretty good.
The content was dry and examples are limited (mostly to BMW only). Also, some concepts are referred to often from the beginning of the book that only get explained much later, I think their is an opportunity to improve the content flow and to tighten it up.
It is very easy to have an idea .. it is also easy to create a proof of concept for an idea .. but turning that PoC into a product requires a major shift in focus. The book provides many insights about the challenges teams face, when they turn from projects to products.