Episode 124: Talking Testing with Anne-Marie Charrett

16069825102_aa54010a22_zCraig is at YOW! Conference and catches up with Anne-Marie Charrett who is well known in the testing community as a trainer, coach and consultant but also for her support of the community:

  • Don Reinertsen talk “Thriving in a Stochastic World
  • Context-Driven Testing
  • Testing is a verb – it’s a doing thing and not an output, but the challenge is you cannot see doing
  • Anne-Marie’s class in Exploratory Testing
  • Where there is risk and failure, there is a job for testing
  • Exploratory testing – the key is feedback and using the learning to feedback into the next test
  • Agile testing – don’t try and test everything and don’t try and automate everything either, rather adopt a risk based approach
  • Unit testing – the usefulness depends on the programmer and the context and figuring out what you are trying to achieve
  • Sydney Testers Meetup
  • Speak Easy – Speak Easy is a voluntary program designed to increase diversity in tech conferences through dedicated conference spots, mentoring and events
  • YOW! WIT Program
  • WorkVentures – training marginalised youth
  • Testing challenges include microservices (the risk of bounded context and breaking things down and missing the whole) and working together as developers and testers
  • James Lewis podcast “Episode 120: Microservices & The Lean Enterprise with James Lewis

TheAgileRevolution-124 (39 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 109 – The Art of Agile Fluency with James Shore

JamesShoreCraig and Tony at the Agile Australia conference sit down with James Shore, best known as for his work as author of “The Art of Agile Development” and co-creator of the Agile Fluency Model and talk about a wide range of Agile topics including:

  • Java Modeling in Color with UML” book mentioned Feature Driven Development (an Australian Agile method!), learnt a valuable lesson to pay attention to the financials and, no matter how much you talk to your customer, seeing is not enough (they need to use it)
  • Extreme Programming Explained“, both editions are the same problem but coming from different experiences with the benefit of seven years of experience
  • the bulk of the “Art of Agile Development” book, particularly section 2, is mostly online, the major thing that probably needs to be updated is the section on customer testing
  • Agile Australia keynote “The Reward”
  • language hunting – there are multiple levels of language proficiency and you can be fluent at any one of them – proficiency is good, but to be really good you need fluency
  • Agile Fluency whitepaper
  • the agile fluency model is not a maturity model, it is about finding the right bus stop
  • Marick’s Missing Manifesto (the things missing from the manifesto) – skill, discipline, ease and joy
  • fluency comes more from the organisational investment than the team, so if you are not seeing fluency look at the organisation first
  • one star is doing Scrum well – with dedicated effort in 2-6 weeks, two stars with mentorship in 3-9 months, three stars takes a lot longer
  • the model is aspirational, so the barriers are high
  • Gamasutra Games Outcomes Project
  • next steps for the model is to share the diagnostics with organisations to help teams compare, contrast and grow
  • “Bloody Stupid Johnson Teaches Agile” with Arlo Belshee
  • the model will work regardless of the method used, its a way of looking at where you are at and not how you do it
  • we should take anybody who fits into the values of the Agile Manifesto
  • Let’s Code JavaScript” started as a Kickstarter, now 300+ episodes
  • Quixote project allows you to test drive CSS and refactor it

TheAgileRevolution-109 (43 minutes)

Episode 95: User Story Mapping (Something Something) with Jeff Patton

JeffPattonAfter chasing him across the east coast of Australia, Craig sits down with Jeff Patton at YOW! Conference in Sydney. Along the way they fail to remember the subtitle of Jeff’s “User Story Mapping” book and talk about:

  • Art school dropout to software developer to early Extreme Programming
  • Extreme Programming Explained” by Kent Beck (and we agree the first edition was the better version!)
  • One of the secrets to success is having a great relationship with customers
  • Early Agile colleagues included Eric Evans (“Domain-Driven Design“), Joshua Kerievsky (“Refactoring to Patterns” and Industrial Logic), Rob Mee (Pivotal Labs)
  • The product decisions on what to build matter most
  • YOW! Talk “User Story Mapping: Discover the Whole Story
  • Story Mapping addressed the problem of losing sight of the big picture when building very small things
  • Larry Constantine and Lucy Lockwood “Software For Use” – task modelling was the inspiration for Story Mapping
  • Impact Mapping was inspired by Effect Mapping
  • There is no way to build a story map and not stand in the shoes of someone using your product
  • They were initially called “stories” not “user stories”, because of the way we use them – it’s not a change in the way we write documents, its a change in the way we work
  • As a… I want… So that… is just a conversation starter, and they need titles!
  • Dependencies in story mapping – the map helps you see in slices, using stories helps you build the thing you need now
  • Passionate Product Owner course
  • The hope of the User Story Mapping book is that people think differently about stories
  • Your job in software development is not to build more crap faster, your job is to change the world
  • Jez Humble “Lean Enterprise” – output and impact
  • What we do now builds on an Agile foundation – but it is more than Agile – we are missing an umbrella term for product centricity
  • Raccoon! – Jeff likes it, but it doesn’t work in mountain states as they knock over garbage cans!

    TheAgileRevolution-95 (43 minutes)

Episode 90: Step Away From The Book

aepCraig and Renee catch up late in the evening to chat about recent Agile articles and events including:

TheAgileRevolution-90 (50 minutes)

Episode 87: Coffee From The Trenches with Henrik Kniberg

Henrik KnibergRenee and Craig catch up with Henrik Kniberg at Scrum Australia 2014 where he tries coffee for the first time in ten years at the Paramount Coffee Project (the best coffee in Sydney according to Renee). Apart from getting his verdict on the brew, they also talk about:

  • First time back in Australia in a long time to keynote at Scrum Australia 2014
  • Craig’s interview “Henrik Kniberg on Lean From The Trenches, Translating the Agile Manifesto and Living Agile” from Agile 2012 in Dallas on InfoQ
  • Scrum and XP From The Trenches” and how the book was written in 3 days
  • Ivory Tower Syndrome – you can get good at describing crap in a believable way if you don’t have connections to reality
  • Kanban and Scrum: Making The Most of Both
  • Spotify – 25 coaches with 25 pet approaches, the culture and the fundamentals in each cross functional team is the same, the purpose of organisations is not make life easy for the manager, it is to make it possible to deliver and learn fast
  • Tradeoffs – consistency vs flexibility in tools such as version control at Spotify
  • Spotify culture – started with Scrum, was fundamentally healthy, created by the mindset of the founders and the first few people
  • Spotify succeeded because the people who work there are passionate about making a great product – making a product where they also the customer – the new problem is keeping empathy for new users
  • Renee still buys CDs apparently!
  • Spotify is focussed on growth not profit – optimise for users loving the product – there will ultimately be one big player
  • Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds” paper and “Spotify Engineering Culture Part 1” and Spotify Engineering Culture Part 2” videos
  • Scaling Scrum Masters and Agile Coaches – gradual ramp up since 2010, each coach has 2-3 squads, coaches are culure workers (a good example of investing in coaches)
  • On coaches, Spotify has shown it is probably harder to multitask roles than teams
  • Crisp – balance of independence versus freedom, runtime environment for consultants
  • Oath of Non Allegience – come to companies with toolboxes – how they work and which one is appropriate for the environment
  • Need some relation to the craft of the team as a coach – need to be open to blindspots
  • Henrik’s verdict on the the coffee… no spoilers, you will need to listen!

TheAgileRevolution-87 (40 minutes)

Episode 83: Making Impacts with Gojko Adzic

GojkoAdzicGojko Adzic “does computers” which means he helps people deliver software and he caught up with Craig on a recent YOW! DepthFirst tour of Australia. Gojko is the author of numerous books including “Bridging The Communication Gap“, “Specification by Example“, “Impact Mapping” and “50 Quick Ideas to Improve Your User Stories“.

  • XP – started with “Extreme Programming Explained” which was really about developers ruling the world – XP is not dead, it won!
  • TDD has crossed the chasm to mainstream
  • Sturgeons Law – 90% of anything is going to be crap
  • Continuous integration and automation has opened up a world of possibilities
  • “Bridging the Communication Gap” – about finding ways to break dysfunctional processes in organisations
  • Agile Testing” by Lisa Crispin and Janet Gregory
  • The most valuable companies in the world are software companies
  • It’s more about the right people being involved rather than narrowly defined roles
  • “Specification by Example” – a collaborative way of coming up with good requirements and tests involving a cross functional team
  • Pschologically people perceive that tests come after development – in that case you have already failed
  • BDD – no canonical definition, would love BDD and SBE to be the same thing
  • “Impact Mapping” – based on a Swedish interaction design process – about setting goals and strageies
  • Impact Mapping uptake outside of IT – Marcus Hammarberg on Doctors in Indonesia and Ahmad Fahmy on helping orphanges in Egypt
  • “50 Quick Ideas To Improve Your User Stories” – a lot more to good user stories than just a template
  • Hamburger Slicing – last resort technique for technical story breakdown to think about options for value
  • Product Management is the big missing piece – teams could benefit from doing this better
  • As an industry we produce too much software – need to change the percentage of software that can achieve something big

TheAgileRevolution-83 (45 minutes)