Our fail wall has failed because it was taken down for saying fail wall. This is only a reasonable reason in a earthquake zone after a mayor earthquake. So what was learned. Timing and wording is important when putting up a fail wall.
Went to the second code kata focused on Test Driven Development at Adscale. Code katas is a very Agile thing to me. The more exposed I become the more I prefer it to normal sessions and discussions.
The katas are:
Focused on working software.
Face to face.
To learn with using close collaboration.
The focused on doing.
Fail fast and learn from it.
Set for continually improving.
Definitely going to the next one.
Antoine de Saint Exupery wrote: As for the future, your task is not to see it, but to enable it.
This talk has a nice explanation of the fragility of large IT projects and large top down organizations.
Ended the year with a good relaxed retrospective. In the last sprint we over delivered on the last day. Which set a great tone for the retrospective and the end to the year break.
But I also did a simple retrospective for my year. It set me up for a relaxed year of end break. It also helped me set some goals for next year.
Try it if you have time.
Found this great section from mythical man month.
“First, my wife, my colleagues, and my editors find me to err far more often in optimism than in pessimism. I am, after all, a programmer by background, and optimism is an occupational disease of our craft.”
Very appropriate section to explain “Optimus prime” then.