Episode 126 – Agile Snotfest

Renee has been busy being sick (and Tony and Craig are sick of being busy) and thus it has been a long time between cough syrup for our Revolutionists…

TheAgileRevolution=126 (64 minutes)

Episode 114: The Responsibility Process with Christopher Avery

caveryCraig and a late-arriving and quietly spoken Renee talk to Christopher Avery, author of “Teamwork is an Individual Skill” and the visionary behind The Leadership Gift and The Responsibility Process, at Agile 2015 in Washington, DC:

  • Management science says that the problem of business performing highly and being profitable and people having a life at work are highly at odds with each other, Agile has challenged that
  • Organisational Agility and self organising teams have been around since the late 80’s / early 90’s
  • Keynoted the first combined XP / Agile Universe Conference in Calgary 2004
  • The Responsibility Process is now in 26 languages, including Klingon
  • The Responsibility Process is a naturally occurring pattern that occurs in our mind that shows how we respond to upset or frustration in ways that we either cope with it or take responsibility to learn and grow
  • Correlation between The Responsibility Process and the 7 stages of grief
  • You go through each stage, even if it is for a microsecond
  • The mental state of responsibility is available to you all the time
  • Listen for yourself saying “I have to…” then catch it and change it to a statement you are willing to own like “I am…” or “I choose…”
  • The Responsibility Process Game – each day score yourself for when you heard it, said it or caught it
  • Research started in 1984 and collected through participant observation and interaction
  • “The first job of a leader is to define reality” Max De Pree
  • First principle of leadership of The Responsibility Process – “No group in an organisation will consistently operate at higher levels of responsibility than the people to whom they report”
  • The Leadership Gift program for individuals via christopheravery.com and corporate solutions as well via Partnerwerks
  • The Responsibility Process book (coming soon)

TheAgileRevolution-114 (28 minutes)

Episode 113: GreenHopper Handyman Folio with JC Huet

JCHuetCraig and Renee, sitting on the banks of the Potomac River on a sunny but slightly windy day at Agile 2015, they catchup with JC Huet, creator of GreenHopper (renamed to JIRA Agile and post-podcast now JIRA Software) and Tempo Folio:

  • Craig was apparently the first client of GreenHopper that was built in a basement, now JIRA Agile is the most popular JIRA add-on with over 500,000 users, used by more than 80% of JIRA users
  • the idea was to have a tool that brought bugs into software management
  • the name GreenHopper represented the Green company branding at the time, and Hopper was for cards hopping between columns
  • a shout out to our friend Nick Muldoon (who is now writing Atlassian plugins at Arijea)
  • Tempo Folio plugin is about supporting cost management, including time sheeting, estimation, forecasting and allocation
  • time and dedication and about three months is all it takes to create an Atlassian plugin (and JC challenges Renee to write her own WSJF plugin)
  • hippies, not EP’s!
  • versions on frameworks are good, means feedback changes are coming

TheAgileRevolution-113 (34 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 111: M&Mailbag

peanutmmCraig and Renee, sitting in a shoe-box sized hotel room in Sydney eating peanut M&Ms, decided to rustle through the mailbag and answer a bunch of outstanding questions.

Note: this episode is not sponsored or endorsed by M&Ms but we certainly enjoy their product!

Crossing The Chasm

  • more and more organisations seem to be crossing the chasm to Agile, but too many are still just doing and not being Agile
  • inimal viable product (MVP) is still the trend word, the next stage is Minimal Viable Experience and then Minimal Viable Robustness to Minimal Marketable Product and finally Continuously Evolving Product
  • Enterprise Transformation Meta Model
  • Agile is a true north concept, not sure that you will ever get there

Suggested reading list on where to start with Agile:

What certification should a new Scrum Master get:

Building your own scaled framework

  • Holacracy and Reinventing Organizations
  • need to answer questions around ensuring quality, growing capability, benefits realisation, etc…
  • at what level do the questions need to be answered
  • Minimal Viable Organisations
  • scale on the operational cadence of the problems of the organisation, not following a framework
  • how often do we check that our approach is meeting our needs

Visualising business analysis in a Scrum team

  • 3 Amigos approach
  • call it what it is if you’re sprint length is longer than it is
  • focus more on Kanban flow

Reading List

  • Renee is reading about climate change (and how that applies to Agile) including “This Changes Everything” by Naomi Klein
  • Craig is reading “CTRL-SHIFT” by  Jessie Shternshus and Mike Bonifer

TheAgileRevolution-111 (71 minutes)

Episode 108 – SAFe from the Source with Dean Leffingwell

DeanLeffingwellRenee, Craig and Tony (with a lurking Em Campbell-Pretty) in a very busy corridor with random bells ringing, catch up with Dean Leffingwell, author of numerous books including “Agile Software Requirements” and “Scaling Software Agility” and the creator of the Scaled Agile Framework (SAFe) in a very candid discussion:

  • the journey to SAFe included as a developer building the Indiana Jones and the Temple of Doom ride and infusion pumps and generally a mission to make quality better
  • epiphony around Agile was the step change around how teams perform and how they like their work when they perform better
  • not everything that is old is stupid, “we are discovering new ways of developing software” and we need to ask ourselves are we still discovering
  • Scrum is the only method that defines what a software team is (roles and size)
  • SAFe is not a war it is a mission to improve outcomes
  • need to provide leadership to agile learning, SAFe is a body of knowledge and a set of patterns that helps simplify learning
  • the differing viewpoints on SAFe are because the stakes have gotten higher, Agile is a big business and hence other approaches need to defend their turf because we are in a competitive market
  • they don’t defend SAFe – we publish case studies, talk about it and implement it, we have to take the pragmatic approach to help people succeed
  • SAFe is versioned because we record the best knowledge we have at the time and Dean is an author, but it has also allowed change management
  • SAFe will always support two versions in the market, including courseware and the big picture, the blog is kept fully up-to-date
  • SAFe LSE was a fork for SAFe for Lean, Software and Systems Engineering and allows for innovation, most of it has been collapsed back to the main framework
  • the framework is free (and will remain so)

TheAgileRevolution-108 (30 minutes)

 

Episode 106: Turning the Agile Ship Around with David Marquet

DavidMarquetTony, Renee, Craig and special guest host Tyson Nutt catchup with David Marquet, author of “Turn The Ship Around!” and the “Turn Your Ship Around” companion workbook at the Agile Australia conference and talk about how similar a nuclear submarine and an Agile team really are:

  • leadership is not about telling people what to do and how to do it
  • all investments in human beings are long term
  • the approach spread from the bottom up, now the book is on the official reading list of two Navy’s (including New Zealand)
  • “I intend to” does not mean they get to do it – gives psychological ownership and to spark the conversation
  • thinking out loud is about saying what is going on in our head, this even works when teaching your children how to drive!
  • feed the beast – don’t respond by hiding, feed them with as much information as you can as data puts you in control
  • you can’t empower people, you can only unempower them
  • you give control while ensuring competence and clarity
  • whilst not telling people what to do can be good for their learning, sometimes you just need to tell people what to do (in the absence of competence and clarity)
  • good to have you team hold you accountable when you fall back to old habits
  • deal with the “frozen middle” by giving them decision making authority they previously didn’t have
  • when learning about a new team ask “what do you hope I will change” and “what do you hope I won’t change”, this is easy when you have not created the culture
  • “I imagine a world where we all find satisfaction in our work” – you need embrace your fears, on a submarine that can be fear of death
  • need to seek permission to proceed and embrace feedback rather than pursuing signoff
  • instead of saying “are you sure?”, ask “how sure are you?”
  • David is working on a couple of new books – a book of success stories and a colouring book
  • when talking to yourself, use the third person for motivation
  • signup for a weekly leaderhip nudge on David’s website

TheAgileRevolution-106 (40 minutes)