I feel as though my body's falling apart. Muscles are tight, eyes are heavy, limbs feel like they could just drop off at any moment. It is the end of the week and I am
super-tired. Tiredness is a ruffian sometimes: he creeps up behind you, tiptoeing like a medieval pickpocket, waiting to duff you up. And then he does, whacking you round the head with a yawny stick, stealing your efficiency, robbing your ability to words use in right order the in... and all the rest of your exhausted faculties while he's at it. Cad.
Alternatively, it may be because today I sat through a six hour planning meeting.
Yes (sigh) who knew when we embarked on our quest as
Team Spamalot, that we would encounter such lengthy discussion upon our travels? Who indeed squire, could have predicted the discourse in meeting room F on a steadily darkening afternoon?
I must admit actually, that I did know it would be that long. When I explained it to a friend of mine yesterday, she was taken aback by the thought of spending six hours in a planning meeting. For some reason by way of explanation, I then went on to explain
Planning Poker to her, and she recoiled in a kind of incredulity.
"That is
random!" she said, and not in a quirky interested way. It was more as though she'd just seen a spider wearing a tiny hat.
So I thought, tonight, as I sit here aching all over, that I'd do my best to explain Planning Poker. If you're into Agile engineering, or you know some zany software developers, this will come as no surprise. You may even have played Planning Poker yourself. Lucky you.
Planning Poker is a way of estimating a whole bunch of tasks in a project.
Firstly, your team writes down every single task they can think of which needs to be complete for the project to be considered finished. Today it was the Professor's turn to scribe the tasks upon the whiteboard. That took about an hour for each feature, believe it or not.
Then, the whole team goes over the tasks again, one-by-one. However, this time, each of the team members is given a pack of
Planning Poker Playing Cards. These are cards which each have a number printed on them: 0, 1/2, 1, 3, 5, 8, 13, 20, 40, 100 or the infinity symbol. As you go through the tasks on the whiteboard, you have to pick a card from your pack which you think represents the complexity of the task. Everyone does the same; each member of the team placing their cards face down on the table. When ready, the team members then flip their card over to reveal their numbers.
The idea is to reach a consensus. Using some complicated algorithm, the score of each task gets translated from 'complexity' into 'how long will it take' and a bright spark somewhere adds up the numbers to get a ballpark figure about how long the project will take as a whole.
What it looks like to a casual observer, is a load of software developers playing cards in a meeting room. That's what it looked like to me when I first played Planning Poker. What's more, my problem is that I don't have a clue how difficult it is to deploy a bit of UI or rewrite a 'milter'... What in the world is a
milter anyway? I don't know what a unit test does and I couldn't care less about validators, consolidators, motivators, rotivators, flibberty-gibbets or howdy-dooberiees.... (I made some of those things up by the way).
I'm a technical author. I live in the front end of the design where the user skips about on the grass, clicking checkboxes and expanding drop-down lists. Out here in the sunshine, the blissful users and I, we're unaware of the horrors that lurk beneath the soil, the complexity of the ecosystem that's working under the lawn to keep it green and fresh... at least while it's working, anyway, we don't really care.
The first time I played Planning Poker, my estimates were so wildly out I may as well have just played the infinity card for every task. Today I was a bit more with it.
That's really all there is to Planning Poker. Was my friend right? Is it a bit weird? Oh what fun. All you non-software types, you're really missing out on big-time entertainment with your normal lives and your enviable ability to socialise.
I'm off to sleep before that scoundrel from the middle ages comes back for a second round of fatigue-inducing muscle-ache.