Episode 134: Unicorns, Distributed Teams and Agile User Groups with Mark Kilby

Craig is at Agile 2016 in Atlanta and catches up with Mark Kilby, an Agile Coach at Sonatype and co-founder of Agile Orlando and Agile Florida. Along the way they discuss:

TheAgileRevolution-134 (30 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 132: Usability Made Easy with Steve Krug

Tony, Craig and Renee are at Agile Australia and catch up with Steve Krug and talk usability and along the way try to figure out whether Tony is lean, agile or just old…

TheAgileRevolution-132 (27 minutes)

Episode 131: Program Management Envato Style with Adrian Fittolani

Renee, Tony and Craig are at Agile Australia and sit down with Adrian Fittolani from Envato and discuss program management and monte carlo simulations. Renee also makes an estimate that is super accurate!

  • Envato – a marketplace for creative assets
  • Lisa Frazier talk at Agile Australia “Leadership in the Digital World
  • utilise bottom up program management at Envato, they have 4 main themes as a company and use self organising themes to meet those themes
  • had to evolve from co-located teams as could not find local resources, they now have any person working in any team wherever they are and make that work, they try to keep teams in close timezones and use asynchronous communication tools, have a policy to work anywhere and additionally a policy to travel and work from anywhere in the world for 3 months
  • the teams responsibility is to radiate program status, currently using a short document with a timeline view
  • launch wall for important items kicking off in the next 2 weeks – helps eliminate surprises
  • project is where more than one team is involved, form a circle around the project (like holacracy)
  • Renee and Craig’s talk at Agile Australia “Coaching Nightmares: Insights We Can Learn from Gordon Ramsay
  • Adrian’s talk at Agile Australia “Better Project Forecasts without Estimates – The Monte Carlo
  • monte carlo simulation- replace subjective estimation techniques that most projects use and rather use a lean approach of takt time to model a project teams delivery
  • takt time – the drumbeat, the time it takes for a process to deliver to another process (e.g. how often a car comes off the production line or how often a story is delivered)
  • value of monte carlo is that it is non-subjective as well as allowing you to decide on the spread of risk you are prepared to take
  • Adrian’s article “Agile Project Forecasting – The Monte Carlo Method” and the associated link to the Takt Time Project Simulation spreadsheet

TheAgileRevolution-131 (28 minutes)

 

Episode 130: Agile Australia 2016 Vox Pop #2

Craig and Tony are roaming the conference floor again at Agile Australia in Melbourne talking to more interesting people in the Australian Agile community:

The Agile Revolution-130 (15 minutes)

Episode 129 – Agile Australia 2016 Vox Pop #1

Picture1Craig and Tony are at Agile Australia in Melbourne and do a lap of the convention centre floor:

The Agile Revolution-129 (13 minutes)

Episode 128 – Elabor8-ing the Agile BA with Ryan McKergow

Craig chats with Ryan McKergow, a Business Analyst and Agile Consultant at Elabor8, at the YOW! West conference in Perth about being an Agile BA:

  • Business Analysts work with business people to understand the problem they want to solve and then work with developers to take those expectations and help them build the system
  • Writing stories and requirements is the boring part of the job – the exciting part is getting different people problem solving together
  • Paul Rayner’s YOW! West “EventStorming” keynote and Craig’s brainwave around Value Stream Mapping 
  • Ryan’s talk “Don’t Be A Zombie Reading Your Stories…” at YOW! West
  • Story Kickoff – having a conversation at the start of a story (one of the three C’s), get the whole team in front of a whiteboard and drawing it out
  • Reduce the amount of time between analysis and development as much as possible, try not to have a lead time of more than one sprint ahead where possible
  • The further ahead you complete analysis, the more likelihood you will introduce waste and rework
  • Showcases and review sessions are a good engagement piece to replace traditional signoffs and to build trust
  • Document conversations as acceptance criteria within stories, but the tool or document does not replace conversations
  • Best way to learn new approaches is to give it a go
  • Eventstorming, customer journey mapping and design thinking are good tools

TheAgileRevolution-128 (25 minutes)