<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Agile 2009 Monday Conference Sessions that catch my attention</title>
	<atom:link href="http://agilepainrelief.com/notesfromatooluser/2009/08/agile-2009-monday-conference-sessions-that-catch-my-attention.html/feed" rel="self" type="application/rss+xml" />
	<link>http://agilepainrelief.com/notesfromatooluser/2009/08/agile-2009-monday-conference-sessions-that-catch-my-attention.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=agile-2009-monday-conference-sessions-that-catch-my-attention</link>
	<description>Best practices for your goals</description>
	<lastBuildDate>Sat, 19 May 2012 03:39:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Jesse Gibbs (Atlassian Employee)</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2009/08/agile-2009-monday-conference-sessions-that-catch-my-attention.html/comment-page-1#comment-56</link>
		<dc:creator>Jesse Gibbs (Atlassian Employee)</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2009/08/agile-2009-monday-conference-sessions-that-catch-my-attention/#comment-56</guid>
		<description>&quot;Effective code reviews in agile teams&quot; is being delivered by members of Atlassian, but I hope that doesn&#039;t deter anyone from attending.  The focus of the talk is how to make code review an integral and non-burdensome part of an agile process.  At Atlassian we&#039;re of course biased towards using a tool-based approach to code review, and towards using Crucible, but that doesn&#039;t mean you can&#039;t have an effective process with other tools such as Smart Bear Code Collaborator, ReviewBoard, etc.  If you&#039;re team is still holding meetings to do code reviews, or if you don&#039;t do them at all because they take too much time, then I recommend checking out this talk.  Tool-assisted code review is a great fit for teams using an agile process, especially if they are distributed like we are at Atlassian.
</description>
		<content:encoded><![CDATA[<p>&#8220;Effective code reviews in agile teams&#8221; is being delivered by members of Atlassian, but I hope that doesn&#8217;t deter anyone from attending.  The focus of the talk is how to make code review an integral and non-burdensome part of an agile process.  At Atlassian we&#8217;re of course biased towards using a tool-based approach to code review, and towards using Crucible, but that doesn&#8217;t mean you can&#8217;t have an effective process with other tools such as Smart Bear Code Collaborator, ReviewBoard, etc.  If you&#8217;re team is still holding meetings to do code reviews, or if you don&#8217;t do them at all because they take too much time, then I recommend checking out this talk.  Tool-assisted code review is a great fit for teams using an agile process, especially if they are distributed like we are at Atlassian.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Levison</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2009/08/agile-2009-monday-conference-sessions-that-catch-my-attention.html/comment-page-1#comment-57</link>
		<dc:creator>Mark Levison</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2009/08/agile-2009-monday-conference-sessions-that-catch-my-attention/#comment-57</guid>
		<description>Jesse - thanks for the reply. My remarks were not well considered every Atlassian Employee I&#039;ve encountered so far was decent. However the outline for the session really doesn&#039;t make clear that this approach would work well with any other tool, its not too late to amend it.

Better stated I don&#039;t think tools are the best way to conduct a code review: &lt;a href=&quot;http://www.notesfromatooluser.com/2006/12/online_code_rev.html&quot; rel=&quot;nofollow&quot;&gt;http://www.notesfromatooluser.com/2006/12/online_code_rev.html&lt;/a&gt; as you see I&#039;ve being saying it for years.

The usual caveat applies if your distributed you will likely need a tool, but otherwise I don&#039;t like tools getting in the way of humans. How often do you see email exchanges with people who sit 5 ft apart.
</description>
		<content:encoded><![CDATA[<p>Jesse &#8211; thanks for the reply. My remarks were not well considered every Atlassian Employee I&#8217;ve encountered so far was decent. However the outline for the session really doesn&#8217;t make clear that this approach would work well with any other tool, its not too late to amend it.</p>
<p>Better stated I don&#8217;t think tools are the best way to conduct a code review: <a href="http://www.notesfromatooluser.com/2006/12/online_code_rev.html" rel="nofollow">http://www.notesfromatooluser.com/2006/12/online_code_rev.html</a> as you see I&#8217;ve being saying it for years.</p>
<p>The usual caveat applies if your distributed you will likely need a tool, but otherwise I don&#8217;t like tools getting in the way of humans. How often do you see email exchanges with people who sit 5 ft apart.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wojciech Seliga</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2009/08/agile-2009-monday-conference-sessions-that-catch-my-attention.html/comment-page-1#comment-58</link>
		<dc:creator>Wojciech Seliga</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2009/08/agile-2009-monday-conference-sessions-that-catch-my-attention/#comment-58</guid>
		<description>I hope that no participant of our talk today had impression that this session was like a vendor talk. Sure, we based demos on Atlassian tools, but it&#039;s just because we happen to use them on a daily basis and we could present something real and hopefully interesting. However I mentioned a few times that _any_ tool could be used instead. So it was not about tools, but rather about best practices and pitfalls.

@Jesse: thanks for the explanation.

Cheers,
Wojciech Seliga
</description>
		<content:encoded><![CDATA[<p>I hope that no participant of our talk today had impression that this session was like a vendor talk. Sure, we based demos on Atlassian tools, but it&#8217;s just because we happen to use them on a daily basis and we could present something real and hopefully interesting. However I mentioned a few times that _any_ tool could be used instead. So it was not about tools, but rather about best practices and pitfalls.</p>
<p>@Jesse: thanks for the explanation.</p>
<p>Cheers,<br />
Wojciech Seliga</p>
]]></content:encoded>
	</item>
</channel>
</rss>

