wiki.accu.org

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
Back to [[conference:committee:2015-proposals]]\\
\\
**Title**: Coding from Examples - A Dojo\\
**Proposer**: [[2015:Wim Heemskerk]]\\
**Proposer**: [[2015:Martin van Dijken]]\\
**Type**: Hands on Workshop\\
**Duration**: 150-180 Minutes\\
**Description**: \\
This coding dojo will let you experience Behaviour Driven Development and Specification by Example from a coding perspective. We will hand out a set of properly-drafted scenarios with the rules to a small game. Using these scenarios, you will experience what it feels like to work inwards driven by acceptance tests. You will walk away from this dojo knowing what (A)TDD from the outside in feels like. Warning: this just might make you like TDD.\\
\\
It is hard to get up to speed with Behaviour Driven Development, although the concepts are explained easily enough. To do it right, you have to learn how to interview your business users, choose your examples, properly write them up as scenarios, choose a framework, and only when you’ve got all that covered, you get to code to your scenarios. For this dojo we’ll be sure to arrange all these preparations for you, so you can hit the ground coding.\\
\\
We will be coding, which we'll prepare for Java. So please bring your laptop with your favorite IDE (or hope you can pair up with someone who did..).\\
\\
Room setup\\
Group of tables to group around in (2 - 4) pairs with electricity for laptops, beamers, flip-over.\\
\\
Group size\\
We're comfortable working with 24 participants (12 pairs).\\
\\
Outline\\
Brief intro, several rounds of hands-on coding on (a digital version of) a board game and discussing what we’ve just covered. Plenty of tricks (i.e. next iteration specs) handy to trigger thought on adaptability and approach and to create a worthy learning experience for different backgrounds / personal experience levels.\\
\\
We will be as focussed on the overall process of working from examples as possible for a hands-on dojo, including concerns such as architecture and adaptability (achieved via DDD?). We will encourage people to pair up including the non-(Java)-coders in the audience; this should be an interesting exercise for one Java coder pairing with someone else too (be it a programmer used to a different language, a tester, an analist, an agile coach, etc.)\\
\\
JJ: They write: Sanity check. We're experienced presenters / hosts, but you don't even need to go by that: after much preparation, this actual dojo had its first try out last night (see http://www.meetup.com/agileholland/events/212236952/ ) and was received very well; experienced as both educating (in what participants described as a novel and useful direction) and fun. We got great feedback and have got plenty of tweaks in mind ourselves, but meanwhile it stood its ground with ease. Real world test successful, confident now in recommending it to you for Accu 2015. And before we visit you, it will have featured at the XP Days Benelux as well (late November in the Netherlands), which will no doubt help us hone it even further.\\

JJ: They write: more details available on request. \\

JJ: They write: If 24 people this is too few, let's discuss. We can probably find ways to double it, but it would be good to have an idea in advance as it will affect how we should run the workshop (and how many USB-sticks to bring :P).