Episode 182: Unlearn-ing with Barry O’Reilly

Craig and Tony are at YOW! Conference in Brisbane and (despite a bin rolling by) sit down with Barry O’Reilly, co-author of “Lean Enterprise” and author of “Unlearn” and they talk about:

  • Reminiscing about Barry’s resume that includes CitySearch (and its competitor Zip2 owned by Elon Musk), Snake, Wireless Pets on Nokia and Lilo & Stitch using J2ME and eventually onto ThoughtWorks
  • Lean Enterprise was written after “The Lean Startup” was released but to explain how it works if you are not a startup and increase experimentation in organisations
  • When people can design good disciplined experiments, you have system to break down problems and grow your system and people
  • Fortune 15 executives and successful startup leaders don’t sit around and ask “if we are doing the framework correctly”- they have their own system, in the same way as Toyota created their own system
  • If you choose an off-the-shelf framework it is just a starting point – you need to evolve your system of work to your context to have a competitive advantage
  • ExecCamp – take execs out of their business for up to 8 weeks with the aim to disrupt themselves in a safe environment
  • Unlearn – we are in an industry where we need to learn but that is not the limiting behaviour, it is our inability to unlearn our existing behaviours that holds us back from getting breakthroughs of higher performance
  • YOW! talk “Why Great Leaders Must Unlearn to Succeed
  • Mean time to discovery – how quickly can you see that an assumption is invalid so that you can then make better decisions
  • How often are you spending time with customers, how are you getting customer feedback and how are you feeding that information back into your system of work to improve it
  • Think big but start small and learn fast – safe to fail experiments
  • Agility is hard…
  • Everybody has a need to unlearn

TheAgileRevolution-182 (37 minutes)

Episode 120: Microservices & The Lean Enterprise with James Lewis

jlewisCraig is at YOW! Conference and has a conversation with James Lewis, best known for his work around microservices at ThoughtWorks. They discuss:

  • Microservices: a definition of this new architectural term” article with Martin Fowler
  • Huge cycle of hype around the term “microservices”
  • You have to run so fast to keep up with the great people at ThoughtWorks you end up accidentally doing interesting things
  • Cruise Control became Cruise that became GoCD which was open source then went commercial and then went back open source
  • Extreme Programming (XP) is complementarianism – the sum is greater than the parts
  • YOW! 2015 talk “Microservices – Building Software that is #neverdone
  • Microservices – systems that are composed of parts that you can independently throw away – the analogy of “My Family’s Axe” (Terry Pratchett)
  • Business and architecture isomorphism – if you look at your architecture you should be able to see your business represented in it and vice-versa
  • Disruption is causing organisations to think about organisational design as well as architectural design
  • Microservices is a style that is applicable for certain circumstances, it is not one size fits all – follow the 16th rule of Unix programming “distrust all claims for one true way”
  • For microservices, Amazon and AWS was the game-changer
  • If you are not building software using the Agile practices these days, you have probably gone down “the wrong trouser leg of history
  • Lean Enterprise is an evolution and description of current thinking
  • Geek crushes on Don Reinertsen and Dan North
  • Agile methods need to focus on flow rather than scaling and structure
  • ThoughtWorks Technology Radar – point in time snapshot on what is going on in current projects, throw systematic darts at the wall, vote on over 300 items to whittle down to 100 items,
  • Stationery driven decision making – sticky notes!
  • Sam Newman book “Building Microservices

TheAgileRevolution-120 (31 minutes)