Sunday, 25 March 2012

Agile NZ Conference - April 2nd/3rd

I'm doing a talk at the Agile NZ conference in Wellington in a week's time - come along if you're in the area, it's bound to be useful if you have any interest whatsoever in the Agile movement.

My talk will focus on the Scrum implementation that we've recently done at CallPlus - here's the blurb:

This presentation takes the audience on a journey; it recreates, as much as possible, a feel for the situation at each phase of CallPlus’ Scrum implementation experience. The intention is for the audience to come away feeling enlightened and empowered. It will mostly focus on the Team and the “human” experience of impementing Scrum.

1. Inception
  • When did we start thinking that Scrum could be a good fit for CallPlus? What was it about Scrum that appealed?
  • Winning the support of the business – how did we win the support of key stakeholders, and how did we accommodate hesitation and uncertainty among business leadership?
  • Analysis of our failed first attempt at compiling a Product Backlog and performing Sprint Planning. What did we do wrong? What lessons did we learn?
  • Realisation that we needed coaching - how we determined what the right fit was for our organisation, how we source and engaged a coach and worked with them to tailor a suitable program.
2. Implementation
  • Second and third time’s a charm – launching Scrum, for real. Running up two Scrum Teams, one after the other.
  • The rocky road to success – repeated incomplete Sprints, Product Owner disarray, Team dissatisfaction, the light at the end of the tunnel, introduction of dedicated ScrumMasters, dedicated Product Owner(s), complete Team buy-in.
  • Our first 100% completed Sprints and the gradual lockdown of the process through Sprint retrospectives (inspect/adapt).
  • Realisation that greater investment in coaching would have oiled the wheels much better.
  • The 6 month milestone – approaching complete business buy-in, and CEO sanity check.
3. Retrospective
  • Analysis of the benefits that Scrum has generated for the business and the development team. What specifically about Agile/Scrum generated these benefits and how can we actively capitalise on that.
  • Analysis of the challenges that we continue to face with Scrum;
4. Looking forward
  • Agile – as is suggested by the Scrum Framework itself - is an ongoing journey of iteration, inspection and adaption. Broadly speaking, how we intend to improve our practice.

Will post the slide-deck following the session - I'm currently busy finishing it off! Here's the programme, the event run across April 2nd and 3rd, and is hosted in Wellington.

Migrating (and Open-Sourcing) an Historical Codebase: SVN-to-Git

I have a SVN repo on my local machine that I have been shoving stuff into since before I knew how to use revision control systems properly (...