Episode 155: Continuous Delivery Culture at Pushpay with Ian Randall

Craig is at YOW! West in Perth and sits down with Ian Randall, Engineering Lead at Pushpay and co-organiser of the Codemania conference in New Zealand and they chat about:

  • The size of the New Zealand banking system and small number of banks makes it very easy to innovate in the payments space
  • YOW! West talk “From Inception to Production – A Continuous Delivery Story
  • The more times you the do the things that are hard and hurt, opens up the opportunities for automation
  • Blameless Retrospective (John Allspaw, Etsy, 2012) – promise that there will be no retribution or consequence for decisions that anybody made during an incident, they made the best decisions that they knew at the time, they were operating in a system that allowed you to make that system in the moment – therefore means that people are not afraid to make decisions because they know they are not held to blame for making a mistake
  • Sidney Dekker “Just Culture
  • 5 Whys – don’t ask why until you reach the root cause analysis, because there are often moire contributing factors and also when you ask why you end up with who (which is blame)
  • WOMing – ensure it works on my machine before it leaves your laptop

TheAgileRevolution-155 (19 minutes)

Advertisements

Episode 149: Continuous Delivery with Dave Farley

Craig, Tony and honorary Revolutionist Pete Sellars are at YOW! Conference and sit down with Dave Farley, co-author of “Continuous Delivery” and they chat about the following

  • There are anti-patterns with doing XP at scale, continuous delivery was born from the learnings from that
  • Continuous delivery is just extending continuous integration to more of the software development practice (and continuous integration requires test driven development)
  • Continuous delivery works because it is the application of the scientific method to software development
  • If you work in an iterative, imperative, experimental way and you take continuous learning seriously and take cycle time as a serious measurement you will naturally drive out agile, lean, systems theory and DevOps
  • YOW! 2016 presentation “The Rationale for Continuous Delivery
  • Most common two ways to introduce continuous delivery to your organisation – need to get cover from senior management to make change or you do it secretly at the grass roots – the fast feedback cycle is important (build feedback in about 5 minutes and ready and deployable in about an hour)
  • DevOps is a terrible name – we are talking about collaborative cross functional teams and it is more than just developers and operations
  • Continuous delivery is focused on shortening the feedback cycle from having an idea to getting the idea into the hands of users and figuring out what our users make of the idea – that’s software development, to do whatever it takes
  • Continuous delivery is working in a way so that my software is always in a releasable state, continuous deployment is if all my automation says my software is in a working state I can just automatically push it to production
  • We have data to show that continuous delivery makes high quality software faster, creates more money for the organisations that use it, reduces defect rates significantly and makes people working in that environment happier
  • It changes the way you design, approach databases and the way you test
  • Scott Ambler’s “Refactoring Databases” book
  • Continuous Delivery tools still aren’t mature enough
  • The deployment pipeline is a seriously strategic resource because it is your only route to Production – need to be able to version and test it like any other Production code
  • It’s as much about the culture of the team than it is about the technology, it frees teams up to do experimentation

TheAgileRevolution-149 (40 minutes)

Episode 133: Rules Are For Pussies!

Craig and Renee are both in Sydney and catch up around the kitchen table to discuss a bunch of things happening in the Agile universe:

TheAgileRevolution-133 (76 minutes)

Episode 122: Learning to Learn with Aino Vonge Corry

ainoCraig is at YOW! Conference and catches up with Aino Vonge Corry who is one of our very few repeat guests on the Agile Revolution. She describes herself as someone who puts speakers on stage, makes developers communicate and messes with the heads of students!

  • Part of the YOW! conference organising committee
  • Important to find examples that relate to all of the students in the class (not just a subset)
  • Microservice lectures – no more than 15 minutes lecture and then a learning activity
  • If there is interactivity then there is a reason to turn up to a live lecture
  • YOW! 2015 talk “A Comment on How We Learn
  • Need to respect and acknowledge that other people take in knowledge at different paces, this is important in activities that we give people time to think
  • People need to relate ideas to the things they are doing now to take new ideas in
  • Working memory takes in new information and as well as decoding for long term memory
  • Research says that we can think about 7 +/- 2 things at a time, but newest research says we can only think about 4 things at a time!
  • Chunk new content or information and then allow people time to process and think
  • Multitasking is a huge misunderstanding, if you are doing two things at once you are only doing them at 40% rather than one thing at 100%, this is a huge problem for people working in computer science
  • Try to figure out your learning preferences, realise you can’t chunk a whole lot of new information at once and ensure you sleep because without sleep you cannot learn effectively
  • Interesting things happening in the culture space right now, Dan North’s YOW! 2015 presentation “Delivery Mapping: Turning the Lights On
  • Polyglot agile highlighted in Craig’s YOW! 2015 talk “40 Agile Methods in 40 Minutes
  • Agile is Dead (Long Live Agility) (Dave Thomas)

TheAgileRevolution-122 (31 minutes)

Episode 112: Inside Spotify with Anders Ivarsson

AndersRenee and Craig are at the Agile Australia conference and talk to Anders Ivarsson, an organisational coach at Spotify, and learn some of approaches that make Spotify tick:

  • Agile Australia talk “Autonomy and Leadership at Spotify” and workshop “Organisational Improvement: Design-inspired Problem Solving”
  • Agile Coaches spend time with squads versus a new role of organisational coach that looks at the culture, ways of working, vision and systemic wastes
  • Spotify is not a model
  • Original Spotify scaling paper, never imagined the spread or the impact
  • Spotify have shared a lot of the things that have worked well, but they do also have challenges as well – one is alignment across teams as the organisation gets bigger so they have been working on visualisation and prioritisation
  • Spotify Culture videos (Part 1 and Part 2)
  • use microservices to ensure that the organisation can work in the way they want to work – great autonomy but a challenge in keeping a consistent design language and customer journey
  • Agile culture is spread throughout Spotify, use what works rather than one particular approach
  • The Oath of Non Allegiance
  • POTLAC – Product Owner / Team Leader / Agile Coach – leadership cell at Spotify
  • use internal blogging to share Agile approaches and patterns, started to recognise the value of story telling
  • Agile Product Management in a Nutshell video – Henrik Kniberg is a genius at making things simple and understandable

TheAgileRevolution-112 (24 minutes)

Episode 101: The Lean Mindset with Mary and Tom Poppendieck

craig-poppendieckCraig catches up with two luminaries in the Agile and Lean space, Mary and Tom Poppendieck at YOW! Conference to talk about agile, lean, rapid feedback, culture and leadership. The discussion points include:

  • Making the link between lean and software development and discovering that waterfall makes no sense
  • The origins of the first book: Lean Software Development: An Agile Toolkit
  • Agile is not lean in software development, Agile is lean in a delivery organisation
  • How long does it take you to put a single line of code into Production?
  • The manifestation of lean really kicked off in 2010 with both the rise of DevOps and the Lean Startup
  • Delivery organisations versus engineering organisations and the journey of Agile
  • Agile has not well addressed delivering the right stuff, solving the right problem and the architecture of rapid deployment
  • Only two goals at ING: Deliver every two weeks and don’t crash production, resulted in rapid feedback loops
  • “The Penguin and the Leviathan: How Cooperation Triumphs over Self-Interest” by Yochai Benkler
  • Latest book: The Lean Mindset: Ask the Right Questions 
  • Create centres of good culture and let people find it, to survive in a competitive environment you need to do something different
  • Goal is to create an environment where people enjoy the challenge of developing software
  • The critical resource to be managed is not capital but the passion and energy of bright and creative people
  • People don’t resist change, they resist being changed
  • Build a change platform, not a change program
  • YOW! 2014 talk – The Scaling Dilemma
  • The military model – leaders have strategic awareness two levels down and situational awareness one level up and the concept of working leaders

TheAgileRevolution-101 (43 minutes)

Episode 2: Squeeze your revolutionist today

SqueezeA fun filled podcast presented by Craig, Tony and Renee covering the following topics:

Quotes:

“I don’t program software anymore, I program people”

TheAgileRevolution-2 (43 minutes)