Episode 117: The Changing Role of a Tester with Mark Pedersen

The Agile Revolution's avatarThe Agile Revolution Podcast

mpCraig is at the YOW! Connected conference and talks to Mark Pedersen, the CTO at KJR, and they talk all things quality and testing:

  • the changing role of a tester in an Agile environment, it clarifies the role rather than making it blurrier
  • in an Agile environment it does not make sense to have a Test Manager role anymore
  • the number of dedicated testing roles are decreasing, but becoming more important and valuable
  • most organisations say that they use both waterfall and agile frequently
  • build your skills in either a quasi analysis / product owner / acceptance criteria role or get up to speed with sensible technical automation tools for your tech stack
  • TDD – good idea but not many organsations practicing it in a dedicated way, unit testing in most industries is a luxury
  • BDD – does not make TDD obsolete, defining acceptance criteria upfront helps understand…

View original post 90 more words

Episode 116: The Heart of Modern Agile

The Agile Revolution's avatarThe Agile Revolution Podcast

heartmodernagileCraig and Tony are sipping a sarsaparilla or two on a balcony in Brisbane and start trying to dissect the state and heart of modern agility:

View original post 92 more words

Episode 115: Connecting Developers & Designers with Chris van Raay & Tom Brodhurst-Hill

The Agile Revolution's avatarThe Agile Revolution Podcast

115At the YOW! Connected conference, Craig sits down with Chris van Raay and Tom Brodhurst-Hill and talks about bridging the gaps between developers and designers:

  • Chris van Raay talk “Bridging the Designer – Developer Divide
  • Tom Brodhurst-Hill talk “Design Driven Mobile Development
  • Typically most organisations have separated development and design teams which results in a very linear process
  • Need simple design documentation as a “single source of truth” because you shouldn’t need to specify styles more than once and it helps reduce effort and obtain a consistent design
  • Use tools such as PaintCode to create a colour palette which serves as documentation as well as a static analysis test
  • Need leadership to ensure there is an agreed approach, set the standards and create discipline
  • When building features need to decide when to leave work that is consistent across features, in relation to design, this should be…

View original post 59 more words

Episode 114: The Responsibility Process with Christopher Avery

The Agile Revolution's avatarThe Agile Revolution Podcast

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
  • Responsibility Process is now in 26 languages, including Klingon
  • 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…

View original post 152 more words

Episode 113: GreenHopper Handyman Folio with JC Huet

The Agile Revolution's avatarThe Agile Revolution Podcast

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…

View original post 34 more words

Episode 112: Inside Spotify with Anders Ivarsson

The Agile Revolution's avatarThe Agile Revolution Podcast

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…

View original post 93 more words

Episode 111: M&Mailbag

The Agile Revolution's avatarThe Agile Revolution Podcast

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:

View original post 323 more words

Episode 110: Every Voice Engaged via Games with Luke Hohmann

The Agile Revolution's avatarThe Agile Revolution Podcast

lukehCraig joins guest co-host Shane Hastie to talk with Luke Hohmann, author of “Innovation Games”, founder and CEO of Conteneo, Inc. and co-founder of Every Voice Engaged at the Agile 2015 conference after his inspirational opening keynote and they chat about:

View original post 30 more words

Episode 109 – The Art of Agile Fluency with James Shore

The Agile Revolution's avatarThe Agile Revolution Podcast

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:

View original post 218 more words

Episode 108 – SAFe from the Source with Dean Leffingwell

The Agile Revolution's avatarThe Agile Revolution Podcast

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…

View original post 170 more words