

Class Registration
At Agile Portugal, I heard Emily Bache (@emilybache) give an inspiring keynote address on the importance of coding dojos to advance the art of programmers and testers. Emily, much like myself, is a strong proponent of test-driven development (TDD), but recognizes that while TDD is easy to explain, it is very hard to put into practice. Coding dojos help address that problem by creating a safe space for programmers and testers to learn more about TDD.
So what is a coding dojo? A coding dojo is when four to eight people meet once a week to discuss code and reflect on how to improve their craft of writing software. Dojos are timeboxed sessions that last from sixty to ninety minutes with at least forty-five minutes of coding. The remaining time at the end of the dojo is spent in a short Retrospective led by the facilitator. Participants are encouraged to do the kata work together in pairs.
Emily also wrote a great book, The Coding Dojo Handbook, to help you start your own coding dojos. In the book, she describes the four simple rules of all coding dojos.
Here is a list of katas from Emily’s github site and another list of katas from the coding dojo site. If you are looking for more katas, just do a google search on “coding katas” and it turns up lots of hits.
Of course, someone on the Internet decided to take the contrary position about the benefit of coding dojos and kata. At least the author took time to craft some well-reasoned positions.
This page is also available in: Spanish
Agile Agile Design Agile SD Book Reviews Burndown Charts Certified Product Owner Certified ScrumMaster Class Design Coaching Collaboration Communication Conferences CSP Fast Pass Daily Scrum Definition of Done Design Excellence Design for Six Sigma Distributed Teams Documentation Español Estimating & Planning Extreme Programming Games Innovation Games Interviews Intro to Scrum Lean Legacy Code Links of the Week Measures Meetings Metrics Migration Movies Open Workspace Pair Programming Personal Planning PMI Powerful Questions Practices Presentations Press Release Product Backlog Product Owner Quality Refactoring Retrospectives Rugby Scrum ScrumMaster ScrumMaster Plus Servant Leadership Simple Design SIMSOC Spain Sprint Backlog Sprint Goal Sprint Planning Sprint Review Stakeholders Task Board Team Test-Driven Development Testing The Core Tools Training Training From the Back of the Room Transitions Travel Uncategorized User Stories Vision Voice of the Customer