Failed fail wall.

August 22, 2012

Our fail wall has failed because it was taken down for saying a fail wall. This is only a reasonable reason in an earthquake zone after a major earthquake. So what was learned? Timing and wording are important when putting up a fail wall.

Advertisements

Code kata TDD

July 4, 2012

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.


Game theory quotes

March 26, 2012

Antoine de Saint Exupery wrote: As for the future, your task is not to see it, but to enable it.


Great talk explaining why we use small self organizing teams.

January 20, 2012

This talk has a nice explanation of the fragility of large IT projects and large top-down organizations.

http://www.thersa.org/events/video/vision-videos/nassim-nicholas-taleb

 


Retrospectives to end the year

December 22, 2011

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 of 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.


Optimism

October 23, 2011

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.


The fist of five

October 2, 2011

The fist of five sounds like an old kung-fu movie. But if you are new to scrum and your team has been failing to make their points for three sprints or more and you don’t have large stories of 13 points or more. You need to look at how you get the team to commit during the planning meeting.

Does the scrum master or project manager decide how many points should be achieved or are you using the fist of five technique?

This is the basic way it works.
You put the sprint backlog on the board and ask the team to do the fist of five.
No fingers mean – no chance.
One finger means – snowball chance in hell.
…(Two to Four is the warmer feelings)
Five fingers mean – hell yes we can.

If anyone puts up anything except a fist with five fingers you remove a story from the bottom and go again.
You only stop when the most pessimistic person says the team will make that number.

An achieving team is a happy team.