Lessons learned from “The Phoenix Project”- part II
This blog is in continuation to Part-1 of my learning from “The Phoenix Project”.
I received amazing response for part-1 which made me excited to write part- 2 for you all. Cheers!
20+ pointers I wrote down in my diary and are taken from this book
11) Making wait time visible
Waiting time for resource, activity, output has a real thing to do with the performance. Before you actually decide that wait time is reason behind decreasing performance or diminishing flow, it is important that you are able to make the wait time visible and find out the actual factors behind the wait time.
12)Team is responsible for the product they develop
The book quoted “ You cannot protect a product when it is already in production. You need to protect it in the processes that create the work product”. If you really want to develop a product that is loved by all, you have to develop it efficiently not just ideate efficiently.
13) Plan-do-check-act
The 4 worded trick is also a part of the “improvement kata”. You need to plan before you execute, once you execute you must validate it. Find what issues occurred, where is the scope of improvement and act upon it.
14) Wait time has all the power to ruin your flow.
The book stated a scenario where 30 secs of touch time took 4 weeks of clock time. All happened because of the non-prioritized work, disharmony within departments and improper estimation. Although the task would have taken 30 secs in normal conditions, these factors made it longer than expected.
15) Security is not an “additional”
The book talks about integrating security into all of your daily work, and no longer securing things after they are deployed. This is actually the best thing to do if you want to save effort on saving what you deployed in production. Security issues can ruin a lot of things, no matter how well the business values are covered.
16) Work won’t be a problem anymore, if we took care of these pointers.
Bill discussed about point 15 and he observed “ Done 30 mins early. This must be a new world record for the shortest time required to agree on anything security related”. Hahahaha, did you get it? Okay, leave it. You will also laugh when you will experience a situation like this.
17) Clear lanes of work, the correct prioritization.
Reducing number of projects in flight can help keep clear lanes of work, so work can go from one work center to the other quickly, getting completed in record time.
18) There is always more than one way to do anything.
If anyone is managing IT without talking about the 3 ways, they are managing IT on dangerously faulty assumptions.
19) Releasing every 15 days is a story of yesterday.
You will never hit the target you are aiming at, if you can fire the cannon only once every 9 months. Stop thinking about civil war era cannons. Think anti-aircraft guns.
20) Agility and raw speed are 2 different things.
Business agility is not just about how good you are at detecting and responding to changes in the market and being able to take larger and more calculated risks.
