<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>kata on Alastair&#39;s Blog</title>
    <link>https://alastaircrabtree.com/tags/kata/</link>
    <description>Recent content in kata on Alastair&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 14 Feb 2016 18:24:36 +0000</lastBuildDate>
    <atom:link href="https://alastaircrabtree.com/tags/kata/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tips for running a code Kata</title>
      <link>https://alastaircrabtree.com/posts/tips-for-running-a-code-kata-at-work/</link>
      <pubDate>Sun, 14 Feb 2016 18:24:36 +0000</pubDate>
      <guid>https://alastaircrabtree.com/posts/tips-for-running-a-code-kata-at-work/</guid>
      <description>Code katas such as the classic bowling game kata by uncle bob are a good way of fostering TDD best practice in your team. Here, in no particular order, are a few hints for running them I have picked up over the last few months.
Start with a subject that everyone knows. For example with the bowling game don&amp;rsquo;t assume that everyone knows how to play and how to score the game.</description>
    </item>
  </channel>
</rss>
