Episode 34: Agile Australia 2012 Wrapup

The Agile Revolution Podcast

Agile Australia 2012Craig and Renee returned from the Agile Australia 2012 conference in Melbourne and share their highlights including:

View original post 30 more words

Agile Australia 2012 Pre-Conference Workshops Review

The day before the Agile Australia 2012 conference in Melbourne was workshop day, and I presented a couple of sessions as well as sitting in on others. There was a good mix of local talent delivering workshops this year. One of my hopes for next year is to make them inclusive of the conference proper somehow, so more people can benefit from and experience them.

First Steps With Agile

On behalf of the Agile Academy, Rene Chappel and I presented First Steps in Agile to a large enthusiastic class (in fact, the class was four times larger than we were expecting and much larger than the numbers I have had in similar classes for the last few years).

New to Agile and wondering where to start or want to know what all the fuss is about? This workshop will start you on your journey and help you become familiar with the core values and principles of Agile. You will gain an understanding of what is meant by the term ‘Agile’ and learn about some of the key practices and processes of an Agile approach (while having some fun along the way!)

Agile Coaching Workshop

The session I presented with Adrian Smith had a capacity turnout  The slides are available in a separate post.

Below is a picture from the workshop where we are getting attendees to move around the room and identify their coaching strengths.

From Agile Australia 2012

Think Like An Agilist

I had one session free and sat in on this session delivered by Jason Yip. The workshop exercises presented scenarios and encouraged participants to practice speaking aloud their process to solving the scenario.

From Agile Australia 2012
  • novices understand the formulas but not what is happening
  • superficial (understand the formula), semantic understanding (understand what is going on), qualitative understanding (know instinctively what is true)
  • “Think like a Commander” – US Army exercise to expose and correct weaknesses
  • learning is not a comfortable experience, it is an experience of confusion
  • sits between classroom study (learning basic concepts) and a full scale simulation (you use your strengths to achieve an aim)
  • use the think aloud protocol
  • fallacy of thinking – can’t help from a learning perspective, you obviously didn’t think about it
  • cognitive themes – things to think about
  • people will never discuss what is working well  when dealing with a problem
  • what someone tells you is mostly their interpretation, they can encourage you to miss things
  • your strengths and weaknesses sometimes blind or endear you to different roles
  • need to practice to answer reflexively

Lean Quest: Establishing A Problem Solving Culture

Last year, I attended a 5 day intensive lean course led by the folks at Lean Quest. The course helped cement a lot of my understanding around Lean and here are some of my takeaways from the course:

Culture

  • the way we execute is the culture we have
  • culture is how we go about solving problems, the way we do our work every day
  • organisations tend to fix problems by: avoiding and defelcting blame, adding resources, calling in external resources, organisation restructures, adding new technology and adding a new layer of management
  • the foundations are our core values and principles as well as our beliefs and assumptions. We can see and observe the norms and behaviours and artifacts. You need to focus on the bottom and the top will take care of itself
  • “you can only see what you can see, you can’t see what’s inside”
  • leaders doing things different will change the culture, need to create an environment where everyone can be successful
  • catastrophes are made up of little problems that are allowed to slide by – it takes 7 problems to happen simultaneously for a plane to crash
  • lean has 3 core values – customer first (start with the customer and optimise the process for the next process), respect for people (engage and enable people, value people over process) and continuous improvement (a thirst for perfection, fix your own work / area)
  • true north – don’t need to get to perfection, but continually heading there
  • lean principles – standardised work, just in time, problem solving, built in quality, visual techniques, culture
  • break the process – by increasing the measure, will expose more problems

Capability 1: Design and Operate Work to Reveal Problems

  • every problem is an opportunity
  • failure is word that people feel uncomfortable with
  • fail quick and often versus do it right the first time
  • reveal problems for the level you control – need to be able to measure this
  • quality starts with the customer (ask them)
  • add quality to the discussion, add value to the conversation
  • quality check at the end, adds no value to the customer
  • pathways break down with the connections between them
  • cycle time – how long it takes
  • takt time – how quickly the customer demands it
  • S5 – sort, straighten, shine, standardise, sustain (also safety)
  • use visual queues, they are all over the place – red line to get to emergency in a hospital, lines in a carpark
  • work is three categories – value added work (something a customer is prepared to pay for – 3% – 4% on average, if you changing fit, form or function you are adding value), incidental work (needs to be done but the customer does not care) and waste (unnecessary activities in the process)
  • continuous improvement to reduce waste and incidental work in a process
  • 7 wastes – inventory, motion (of the person), material movement (of the product), rework, over processing, waiting, over-production (the worst waste because it hides the other wastes)
  • we want problems to surface so we can see them and fix them

Capability 2: Contain and Solve Problems Close in Person, Place and Time

  • if you reward fire fighters, you get arsonists…
  • we don’t teach people how to solve problems very well
  • everytime you problem solve you are making a little more time for yourself
  • a problem is a gap between the expectation and the current state, the key is to set the standard , if you don’t have a standard you don’t have a gap
  • keep lowering the water level and/or raising the standard
  • start with where you are today and measure variation to the standard
  • PDCA – Plan, Do, Check, Act (Deming wheel)
  • 7 step problem solving process (1. define the problem, 2. grasp the situation, 3. plan, 4. do, 5. check, 6. act, 7. conclusions and lessons learned)
  • A3 – used to document the journey in the most concise form possible
  • project charter – an improvement project that is a break from operations
  • SIPOC+M – process level summary (Supplier, Input, Process, Output, Customer + Metrics)
  • COPIS – business level summary (multiple processes)
  • a lag indicator could be a lead indicator for another process
  • fishbone – cause and effect diagram – 4M’s (Man, Method,Machine, Material)
  • pareto chart – line / bar chart that distinguishes in descending order the relative importance of problems
  • “say it with charts” – Edward Tufte
  • 5 Why’s – peel away the layers of a problem and reveal the symptoms that often lead to the root cause
  • 3 why’s in sales is considered interrogative
  • SMART targets – Specific, Measurable, Achievable, Relevant, Time-Based

Capability 3: Accumulate and Share Knowledge

  • knowledge is an asset
  • use a SIPOC+M to grasp the situation or to assess the future state, want to create a SIPOC+M for the repeatable steps (there should not be 100’s of these)
  • SOP – Standard Operating Procedure – leverage SIPOC+M and process flow diagrams
  • use a standard A3 format for reading and reviewing efficiency
  • leaders need to understand the job – need to study it and be able to improve it

Capability 4: Leaders Coach and Develop the Previous Capabilities

  • traditional organisations manage people and results, high performing organisations manage processes

Episode 32: Agile Australia 2012 Kickoff

The Agile Revolution Podcast

Agile Australia 2012Craig and Renee are at the Agile Australia 2012 conference speaker breakfast where they discuss the workshop day, the upcoming conference and their respective talks and a Lean Startup story about monkeys and bananas.

TheAgileRevolution-32 (9 minutes)

View original post

Agile Australia 2012: Agile: Looking Back, Looking Forward: Adapt, Innovate, Collaborate & Deliver

My plenary presentation from Agile Australia 2012 with Nigel Dalton, David Joyce and Simon Bristow called “Agile: Looking Back, Looking Forward: Adapt, Innovate, Collaborate & Deliver” is available on SlideShare.

Agile adoption in Australia and across the world is now becoming more mainstream and, as a community, we are struggling to address the issue of how to take experienced Agile practitioners to the next level, while still supporting those who are beginning their journey. With the “agile” word getting so overloaded, the challenge is to continually innovate without assigning labels or losing focus on our prime objective – to deliver!

Join Craig Smith with Nigel Dalton, Simon Bristow and David Joyce (on the couch) as they explore different viewpoints on all things Agile – then, now and future!

Some of the comments on Twitter included:

@jchyip: #adapt discussion is similar to our Agile cult discussion at this morning’s Lean Coffee. #agileaus

@carolineggordon: Issueing a challenge to the women in the audience at the panel, I want to see one of us up there next year #agileaus — #deliver

@stephlouisesays: Always look forward to hearing @smithcdau at #agileaus -didn’t disappoint! Valuable messages and images that make you think (and giggle!)

@lukasm: Great start to #agileaus Inspiring talk by Dr Fiona Wood followed by a thought provoking panel on where agile is, has been, and going.

@kiwihoria: Are we there yet? There’s no #Agile destination, just a journey.http://ow.ly/i/EYyW #AgileAus

@agilerenee: Hmm not sold that Perth was the highest per capita ad a community – Wellington rocks with 467 people for 200k city #agileaus @smithcdau

@andrewlitvak: Why paper documentation is the worst way to collaborate – no rich interaction, not effective communication #agileaus

@kiwihoria: Is your organisation retrenching to waterfall? Hold stand-ups in stairwells, hide kanban boards under the desk – #guerillaagile #agileaus

@Prash_Sagar: agile will not solve the problems, it will help you identify them @simonbristow #agileaus #adapt

@rowanb: Great to hear @dpjoyce call out “veneer agile”… “doing Agile vs *being* Agile”. Let’s stop saying “doing Agile” #agileaus

@SMRobson: #agileaus @smithcdau agile adoption is like playing Donkey Kong. Level 1 is hard & everyone throws barrels at you…but level 2 is harder!

@kiwihoria: Renew or decline? http://ow.ly/i/EYtO It’s up to us to keep improving teams, products and communities #agileaus

@agilerenee: “our job as a community is to keep renewing the product – the product that is #agile” @smithcdau #agileaus

@SMRobson: #agileaus Nigel Dalton – take agile beyond IT, your job is to work with the business, principles can apply to everyone

@kiwihoria: #Agile job demand increased steadily in AU/NZ – lots of emphasis on Product Management now http://ow.ly/i/EYsd #AgileAus

@andrewlitvak: UX is now a strong focus for Agilists. Woohoo! #agileaus

@rowanb: “At a team level it is job well done but… In terms of business agility, we still have a fair way to go.” @dpjoyce #agileaus

@andrewlitvak: Delivery agility, we’re nearly there… Business agility? Not so much. Yet. #agileaus

@lukasm: Either me or that couch need some stilts! #agileaus

@vivierose: So great to see @smithcdau on the main stage opening #agileaus

@justinhennessy: Great intro from @smithcdau #agileaus

@SMRobson: #agileaus cool potted history of Agile from @smithcdau & even better – lets change it to Raccoon so we get over the name

Agile Australia 2012: Agile Coaching Workshop

My workshop from Agile Australia 2012 with Adrian Smith called “Agile Coaching Workshop” is available on SlideShare.

The Agile Coach is a critical role in helping leaders, teams or individuals understand, adopt and improve Agile methods and practice. Additionally, an Agile Coach helps people rethink and change the way they go about their work. For a individual to be effective in a coaching role, they must poses a wide range of skills and experience. In this workshop we will explore Agile coaching skills in the context of a competency framework and provide participants with lessons from real-world coaching experience. The workshop will provide an opportunity for participants to learn about coaching, identify areas of Agile development and to broaden skills through hands-on group and individual exercises and games.

You will:
» Understand role of an Agile coach and the typical development pathways
» Identify personal areas of strength/weakness in relation to a broad range of Agile and related skills
» Learn situational specific coaching techniques for common Agile dysfunctions
» Understand the use of maturity models in helping teams learn and adapt to Agile
» Understand organisational and role specific Agile challenges
» Learn how to adapt Agile practices to suit team specific challenges

UPDATE: Due to some requests for the competency matrix, a PDF version is available for download