Toronto Project Manager – Paul Henman CSM

Today’s Dilbert is yet another that hits too close to home:

I wrote a brief post saying I was looking forward to the one-day event, and I definitely wasn’t disappointed. I was so engrossed I failed to take any photos but I did take some notes during the day, although I hoped that the presenters’ material would be available sooner. (Speaking of sooner, I know it’s taken me forever to post this recap – I’ve been kept really busy by both my photography and job hunting.) Anyway, on with the show… (more…)

The Agile Tour 2009 hits Toronto tomorrow! [Official site and Facebook page]

I’m excited to be attending, learning more about Agile (there’s always more to learn!), catching up with friends and meeting new people with a shared interest in Agile. I’ve looked at the programme and there are lots of good sessions, but I also want to spend some time networking; it’s going to be a full day!

I’ll be taking my Eee netbook and my camera, so hopefully I’ll be able to record a lot of the information – I’ll be tweeting (must remember to find the hashtag) but my photos won’t appear (on my Flickr stream) for a few days, and then I hope to write a few blog posts on the most interesting topics too.

Who else will be there?

How do you identify a high priority task? I like this answer, found on Merlin Mann’s website:


In Scrum we tend to see tasks (the work breakdown that a team deemed necessary in order to deliver a Story or feature) as equal priority because they all need to be completed in order to say we’re Done.

However Scrum also has the concept of a Product Backlog, which is a prioritised list of Stories (or features) which the Product Owner manages; planning for each Sprint (iteration) begins with the Product Owner describing the top priority Stories.

So maybe this card should say “How do you identify a high priority Story? It’s Done.”