It has been 13 months now since I posted my first entry under the “Scrum / Agile Development” category. That was when I had just been certified as a ScrumMaster and my team was very early on in its adoption of Agile. Since then, I have learned an awful lot, but I haven’t felt like I had enough wisdom to make further postings worthwhile to the few people who read my blog!
I now find myself sitting in the BA lounge in Chicago’s O’Hare airport, returning from the Agile 2006 conference in Minneapolis. Having had a week to think deeply about some of the happenings over the past 13 months, as well as a chance to think about the future, I realised that I have a number of key defining moments that I can talk about in my teams’ Agile learning growth.
If you are in my team, you probably recognise the title “Post Game Huddle” from a few internal mails I sent. I liked how it fits with the Scrum analogy, where working on the products is the “game” and these thoughts are the coaches talk after the game is over. So, I am keeping the title for some forthcoming thoughts about how other teams can leapfrog some of the hurdles that slowed my team down.
This is just an intro, watch out for more entries in the coming few weeks.