Dojoing

The first dojo was a success. There was some of uncertainty still in the air on Thursday but luckily the black clouds stayed away. Experts were there and gave good presentations. They also kept their role all the time which was a nice surprise. All attendees were able to keep their attention the whole session and seemed to focus on trying to solve the problem. I really believe that some of them really learned something. So mission accomplished.

A few more positive things. Questions were good and on the topic. Some of the attendees also stated their opinions on different subjects. When the negative things were enquired we already got some things where we can improve next Friday. So next time only one presentation at a time. And more noise from the people typing on the machine.

For me the session was easy. I tried to give a couple of improvement ideas and guide towards good solution. The feature file we created still needed some fine tuning after the session but still all the relevant things were there. Not bad.

A couple of details. My answer to the "how about the regression and ATDD cycle" question was bad. I should have just tried to explain that the cycle is about getting new features done. The idea on automating the acceptance criterias and working (in small) using TDD then works towards catching regression automatically. When some bugs still get into the product they are then handled according to project's/team's/companies processes. And please note also that this is only my interpretation...

I should have also spent some more time on the business case and purpose of the feature. The "In order to... As a ... I can..." part of the feature. That is an important thing when you think about the feature although not that visible anymore in the implementation phase of it.

Hopefully next time we will also get some nice discussion in addition to actual results. Looking forward to next Friday. Will still create the feature file like promised.