<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Agile Testing with Lisa Crispin &#187; blogs</title>
	<atom:link href="http://lisacrispin.com/wordpress/tag/blogs/feed/" rel="self" type="application/rss+xml" />
	<link>http://lisacrispin.com/wordpress</link>
	<description>Providing Practical Agile Testing Guidance</description>
	<lastBuildDate>Mon, 30 Jan 2012 16:52:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Coders &amp; Testers Together &#8211; a Rant and an Article</title>
		<link>http://lisacrispin.com/wordpress/2009/06/23/coders-testers-together-a-rant-and-an-article/</link>
		<comments>http://lisacrispin.com/wordpress/2009/06/23/coders-testers-together-a-rant-and-an-article/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 15:29:53 +0000</pubDate>
		<dc:creator>lcrispin</dc:creator>
				<category><![CDATA[agile testing]]></category>
		<category><![CDATA[Publications]]></category>
		<category><![CDATA[Transitioning to agile]]></category>
		<category><![CDATA[articles]]></category>
		<category><![CDATA[blogs]]></category>
		<category><![CDATA[testers and programmers]]></category>

		<guid isPermaLink="false">http://lisacrispin.com/wordpress/?p=279</guid>
		<description><![CDATA[Last week I attended SEETEST in Sofia, Bulgaria. The conference was extremely well-organized, and I learned some new things, such as test automation considerations for testing mobile devices, and coordinating agile testing with compliance requirements. There were also some things said that hit one of my hot buttons: whether testers and programmers ought to work [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #333399;">Last week I attended SEETEST in Sofia, Bulgaria. The conference was extremely well-organized, and I learned some new things, such as test automation considerations for testing mobile devices, and coordinating agile testing with compliance requirements. There were also some things said that hit one of my hot buttons: whether testers and programmers ought to work together, versus on separate, siloed teams. </span></p>
<p><span style="color: #333399;">This inspired a rant which I posted (OK, Joey McAllister posted it for me) on my <a title="Rant" href="http://blogs.stickyminds.com/Blogs/tabid/91/EntryId/93/Independent-Testers-Or-Independent-Thinkers.aspx" target="_blank">StickyMinds blog entitled Independent Testers? or Independent Thinkers?</a>. I would love to have comments on your experiences with testers and programmers working together.</span></p>
<p><span style="color: #333399;">Coincidentally, the latest Methods and Tools magazine has an article I wrote on <a title="Coding and Testing" href="http://www.methodsandtools.com/archive/archive.php?id=88" target="_blank">Coding and Testing: Programmers and Testers Working Together. </a>In this article I work through an example of how testers and programmers collaborate to develop new features, similar to the examples Janet and I use in our book. Please check it out along with the other interesting articles in Methods and Tools.</span></p>
<p><span style="color: #333399;">I&#8217;m working with programmers and testers together more than ever on my new team. Right now we are all on a voice chat, with a shared desktop, writing FitNesse/SWAT tests and code together. (OK, I am really just watching, but I&#8217;m learning, and asking questions.)<br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://lisacrispin.com/wordpress/2009/06/23/coders-testers-together-a-rant-and-an-article/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

