The dojo ran again last night, and seemed to go well. This time we started to explore representing a text adventure game. The elements* I gave were never implemented (or even considered beyond the first 5 minutes).
I think there is starting to be an interesting tension between methodologies here. Those that are used to development driven through TDD methods vs. those that are used to traditional methods. Both these groups seem to be being subverted by the time constraints, as people leap in to do the one thing in the problem space that they can immediately see in their 5 minute slot, and so neither methodology leads as each individual pairing over-rules any systematicity. The result is, simply-put, something of a mess. Fascinating.
I am starting to think I should get people to sign ethics forms so that I can properly look at the data for how this is working. It looks like it could produce some beautiful work. Shame this is social and not for my PhD.
---
Interesting Thoughts from Dojo Session 1: Tom, Dom, Jez, James, Joh
Very Interesting thoughts from Dojo Session 2: Tom, Jez
Flickr Photos: CodingDojo
---
One thing which I think we need to explore at the start of the next session is the purpose for the dojo.
- Are people coming to explore a problem space, experiment with agile, learn from other people, show off their programming skills, etc?
- What do people see the purpose of the dojo as: art, practice, learning, teaching, exploring, communicating, socialising?
- Should we be aiming to be 'completing' a task in the time period, or just exploring the start and space?
This should be to open up discussions that have already been happening in the tea-breaks and certainly not to change or formalise anything. At the moment I think there is a very good balance in the various interests and desires of everyone involved. A stated purpose would be limiting and restrictive.
---
* A House, A Cat, A Blue Necktie, A Nodding Dog Ornament, Something Orange, and a Lift.
Comments