To calculate the overall star rating and percentage breakdown by star, we don’t 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.
I read a couple of books before on kanban, but I never really related to what they were about. They were very manufacturing for corporate in approach. This book has a slant towards software development and IT infrastructure, but it is much easier to relate to other fields, including in the public sector.
I have been in IT Operations for many years. Over that time I have discovered the importance of being able to see my work (mine, my teams and my suppliers) such that we can deliver on-time, quality items without killing ourselves. Unplanned work, reprioritisation, illness, incidents and more all take their time on the plans we had laid for that day or period.
I had the pleasure of meeting Dominica when she was referred to me as the best Lean-Agile Operations focused individual around. A referral I treasure and this book substantiates why. Simple, focused, Theory followed by experience followed by examples and helpful exercises. What a great way to learn how to create conversations that matter around the work you are expected to do, are doing, have delivered or want to improve.
We all know that we are constantly being interrupted during working hours, seems we can't ever finish anything meaningful, but why? This book explains in a nice way the time thieves, makes a case for flow metrics. As I read the chapter for flow metrics I measured all the flow time and cycle time, calculated the distribution of my team velocity and was able to prove few things that I knew were true but couldn't actually convince nobody. Just for that I think this book deserves a read.
I wish I had something like this where I could articulate the reasons for delay in a way that everyone could visualise and understand. It is so easy to say Yes but difficult to say No without being able to say and this is why I can't do what you asked unless I have your permisssion to stop work on what I have planned and do this instead.
Some great examples of optimal resource utilisation and how to limit WIP. I love the quote 'Stop starting and Start Finishing'
Having worked with Agile DevOps teams I learned some useful skills for Kanban and starting to call out time thieves. But the inclusion of data-driven operational performance reporting and running effective meetings is what made this stand out and learn new things.