Skip to main content

Sound bites from 'The Phoenix Project' novel


The Phoenix Project is such a riveting story. Being a software developer, it resonated so well with me. Even if you are not a software developer, there is something to be learned from this book. This book shows how important it is to be honest, have integrity, faith, encourage risks and continuously improve in small but meaningful steps. The principles learned from this book can be applied to any industry, process, organization and even relationships. 



I have a few quotes when I was done reading the book.


Automation creed
    If it can be done once, it can be automated for future occurrences. 

    If it needs to be done more than once, it must be automated.

    People before process. 

    Feeling of being in control is an illusion. Let go of that feeling and breathe because you can still succeed when you succeed as a team.



    Four types of work
    1. Business projects
    • Business initiatives
    • Typically tracked by the project management office

    1. Internal IT Projects
    • Infrastructure and IT operations projects
    • Projects required to support the business projects
    • Internally generated improvement projects

    1. Changes
    • Generated by business projects and internal IT projects.
    • Track both business and IT project changes in the same ticketing system

    1. Unplanned work and recovery work
    • Operational incidents
    • Caused by business projects, internal IT projects and changes
    • Always at the expense of other planned work commitments
    • Track them and automate to prevent them

    Wait time formula
    wait time = (% busy) / (% idle)

    The three ways explained
    1. First way
    • Work flows from left to right from development to IT operations to market
    • Maximize flow
      • Small batch sizes of work
      • Small intervals of work
      • Never pass defects to downstream work centers
      • Continually optimize for global goals of the business organization
    • Necessary practices
      • Continuous build, integration and deployment
      • Create environments on demand using the same process to create all environments
      • Limit work in process (WIP)
      • Build systems and organizations that are safe to change by keeping both agile and nimble

    1. Second way
    • Constant flow of feedback from right to left at all stages of the value stream
    • Prevent problems from happening again. By doing this we create  quality at source.
    • Create and embed knowledge where needed
    • Necessary practices
      • Stop the production pipeline when builds and tests fail in the deployment pipeline.
      • Continually elevate the ‘improvement of daily work’ over 'daily work’.
      • Create fast automated test suites to ensure code is always in a deployable state.
      • Create shared goals and shared pain between development and IT organizations.
      • Monitoring to ensure code and environments are operating as designed and customer goals are being met.
    1. Third way
    • Culture that encourages continual experimentation
    • Encourage taking risks 
    • Share an understanding that repetition and practice is the key factor for perfection.
    • Necessary practices
      • Creating a culture of innovation, risk taking and high trust.
      • Allocating at least 20% of dev and IT on non-functional requirements
      • Continual reinforcement that improvements are encouraged and celebrated.

    Identify and focus on
    1. Constraints
    2. Materials
    3. Resources

    Popular posts from this blog

    A @trello board to get kids excited

    My 8 year old just started his summer break. He did so well in school and I am proud of him. He skipped second grade, got into the gold honor roll in every quarter and got a medal for doing that. Last night, I promised to install a new app for him on his iPad mini. I installed Trello and created a board for him while he watched. I showed him how to create cards, add labels to them and move them from To Do, to Doing to Done. I had him create some cards and label them. He could not stop creating cards. I could not convince him to go to bed after that. He created cards for everything he wants to do in the summer and he is not done with creating cards. He even created a card to email a screenshot of his Trello board to his teacher. Later last night, he was still awake in bed when I checked on him. He told me that he wanted to add three more labels - Math, Science and One-on-One. He wanted a label titled 'One-on-one' for tasks that he wants to do with me and he wants one-on-one at
    Read more

    A @trello board to get kids excited - continued

    This is a continuation of the previous post titled - A trello board to get kids excited . At the time of writing this post, the previous post had 198 page views. I wish people commented. I did get some positive feedback on Twitter. The Trello twitter account re-tweeted my tweet and also sent out a second tweet advertising the page. Thank you very much. I hope a lot of parents and kids benefited and had fun as a result. Trello people: Idea - How about a 'Trello Kiddo'? Perhaps you could offer that to schools that give iPads for each kid to take home with them. Get them when they are young. When a kid does something religiously, regularly and feels great about it and can't wait to tell everyone about it, you know you've done well as a parent. We realized that we needed a separate column to keep track of 'Special accomplishments'. Positive reinforcement that you can see with your eyes! Some parents feel like they haven't done enough for their kids, partic
    Read more

    Create #VirtualPrivateCloud, NAT Instance and NAT Gateways on @AWSCloud

    Create a Virtual Private Cloud, NAT instance and the new NAT Gatweay ... and making it all work. This is a YouTube playlist of three videos.
    Read more