Work in progress

Day one of the retreat was definately a learning experience. At the end of the day we ran through a lessons learned exercise, some of the things we thought we might change included...

Trying to do too many new things at once. It's hard to know if we're going slowly because we're new to Ruby / Rails, because we're not getting XP right, or what. Perhaps this should have been a re evolution.

A real customer would really help Laying our hands on someone to spend three days 'being the customer' wasn't really possible. Without that things like the planning game become a bit more like rituals and a bit less like negotiations

More preparation time We've lost a lot of time today due to avoidable issues, like network problems. Had we managed to test this stuff in advance we'd have been able to make better use of our time available for coding.

On the positive side it's good that we're managing to try this. It's good that we are making some progress, however slow. It's good that the local Ruby community is helping out. It's good that we managed to play a planning game, do some work in pairs, get out of the office, have an end of day retrospective, get the working in public thing up and running and spend some time with each other.

These are not small things. And I for one am confident that tomorrow will go rather better than today.