Ah, the one thing Agile and Scrum seek to avoid has struck once more!

Yet again we have a coding task blocking us from moving forward, we thought we had avoided this problem by better defining our tasks however it would appear not. We cannot write code for calculating the residual nitrogen until we have an idea of how the tables are going to be represented and store. Perhaps this should have been designed better but then we have different levels of skill and ability in the group so that is one of those “Oh, we should have thought of that” type problems.

Anyway, while Alan and Stacey were working away on that Rory and I moved on to the third user story and actually managed to take care of a number of the tasks (design and GUI implementation). Was quite nice to see the chart start to go downward on the next story, gave a nice feeling of concurrency (or perhaps that is just John Arnott’s Computer Architecture lectures going to my head!).

The pair programming seems to be going more smoothly this time around, all three teams working hard on their tasks, was a very nice atmosphere.

A couple of quotes from today that made us all smile (after seeing a comic strip about the upcoming Lego online game):

“Learn to build n00b”

“Can I haz ur bricks?”

The Refactor Tractor has been beaten….by Lego!