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 160: Agile Lessons From My Younger Self with John Sullivan

Craig is at YOW! Hong Kong and has a chat with John Sullivan, the CEO at Elabor8, and they talk about his Agile journey in Australia from ThoughtWorks to Sensis to Qantas to MYOB and the challenges and learnings along the way

  • The Agile Revolution episode 159 “What Colour Agile Would You Like Today with Nigel Dalton”
  • “Extreme Programming Explained” by Kent Beck
  • Sensis was a very early corporate in Australia that adopted Agile from beginning to end, moved teams out of the building so they could work uninhibited in an Agile way
  • The technology teams almost always aren’t the problem with product delivery – it is the product team taking an idea from the top to the bottom of the organisation and getting it in a form that is fit for customers
  • Not happy Jan! – Sensis had their focus on print and was not willing to disrupt
  • You need sponsorship and objectives right from the top if you want to make change – otherwise there are reasons why you do what you do and you won’t change
  • Do the things that are the hardest to do because then that gives you the freedom to do the things you want to do
  • Need to stop thinking about Agile as an institutional process
  • You can’t focus on the practices, you have to become Agile and then adopt practices that are the right thing to do
  • In relation to feedback, you need to value people’s effort and return something of greater value than what they put in
  • A real Agile digital transformation is about the shift to provide something that people want to use and then we can monetise it, which means you need to build something people need not what you think they want
  • Need to put teams together for a customer journey as opposed to divisional handoffs – that is an Agile digital transformation
  • John Sullivan’s YOW! Hong Kong talk – “A Presentation to Myself on Organisational Agile Transformations”
  • The theory is that the twelve principles were written to be too strict to apply and too heavy to consume at the time – the manifesto was written to be flexible around those principles – now the manifesto gives people too much slack
  • The Agile Revolution episode 119 “Agile (Raccoon) is Dead with “Pragmatic” Dave Thomas”
  • John Sullivan’s YOW! CTO Summit talk “A Common Vision is a Matter of Principle” where he mentions that platform manifesto
  • We need to stop trading off doing the right thing because the shortcuts drag down the productivity and it becomes an anchor – do the right thing right now, pay the cost, take the ownership and don’t give in on the principles

TheAgileRevolution-160 (51 minutes)

Episode 146: Agile, Architecture and Technology with Rebecca Parsons

Tony and Craig are at YOW! Conference in Brisbane and catch up with Rebecca Parsons, the Chief Technology Officer at ThoughtWorks and the co-author of “Building Evolutionary Architectures: Support Constant Change” and chat about the following:

  • Rebecca’s keynote talk at YOW! “The Past and Future of Evolutionary Architecture
  • Evolutionary Architecture is the next stage on applying Agile practices to software development at the systems level and be able to respond to changes in the environment that affect the architecture
  • Need to determine for your system what constitutes good, fitness functions are the documentation and tests to ensure your system meets those characteristics
  • Need to move the needle on architecture, need to develop tools and techniques to decompose the role
  • Agile Alliance is looking at what it means to truly be an international organisation (there are now affiliates in Brazil and New Zealand), expanding conferences from the large North American conference to OnAgile and Deliver:Agile and member initiatives to support local events such as Agile Open Space, Agile Conference Sponsorship, Community Group Support Initiative and Speaker Reimbursement
  • YOW! CTO Summit talk “The CTO is Dead: Long Live the CTO
  • CTO role is more now to set technical direction by setting up communication channels to mine insights that can be rolled out and presented to the market
  • ThoughtWorks Tech Radar started as a hot technology list of what ThoughtWorkers would love to work on, became a visual radar that is now released twice a year, starts with 250-300 items and they try to get it down to 100 items, something will fade after being in the adopt ring more than twice, the radar is also available as an open source tool or radar as a service
  • Women leave technology at double the rate as men leave technology, mostly because they are not treated well in the environment
  • Anita Borg Institute Top Company for Women Technologists award
  • What does it mean to be Agile in new technologies like machine learning and data science?

TheAgileRevolution-146 (34 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)

Episode 102: The Essence of Microservices (and Agile) with Scott Shaw

scottshawTony and Craig are at YOW! Conference and in the hallway ambush Scott Shaw, the Director of Technology (Australia) at ThoughtWorks and talk about the state of microservices and Agile:

  • Scott’s YOW! talk “Avoiding Speedbumps on the Road to Microservices
  • Microservices are just a different way to build applications that get away from monoliths
  • Beth Skurrie, Evan Bottcher, Jon Eaves case study at YOW! – “The Odyssey – From Monoliths to Microservices at realestate.com.au
  • Essentials for microservices include Domain Driven Design, security and identity and change management
  • Simon Brown talk at YOW! – “Agility and the Essence of Software Architecture
  • Cloud and infrastructure as code has changed the way we look at applications and have allowed microservices
  • The essence of Agile is the team taking ownership of the business success of whatever it is they are building and keeping that ownership over the longer term
  • Microservices take advantage of Conway’s Law – the teams closest to the systems should own them or change your structure to mimic the systems you want to look after
  • There should be no difference between maintenance and evolution – it is all one of the thing that goes towards the success of the business
  • Adrian Cockcroft defines microservices as “a service-oriented architecture composed of loosely coupled elements that have bounded contexts”
  • Microservices should be no bigger than a concept that fits in your head
  • Sam Newman book “Building Microservices
  • Agile approaches that are evolving include Docker and functional programming languages (especially Scala, Clojure and Go), the importance of craftsmanship and skills
  • Defending the Free Internet
  • ThoughtWorks Technology Radar
  • Microservices in a Nutshell by Martin Fowler and James Lewis

TheAgileRevolution-102 (28 minutes)