<?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>david rasch - making stuff work &#187; jira</title>
	<atom:link href="http://www.davidrasch.com/tag/jira/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidrasch.com</link>
	<description></description>
	<lastBuildDate>Mon, 04 Apr 2011 00:53:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Atlassian Jira and Confluence</title>
		<link>http://www.davidrasch.com/2008/03/18/atlassian-jira-and-confluence/</link>
		<comments>http://www.davidrasch.com/2008/03/18/atlassian-jira-and-confluence/#comments</comments>
		<pubDate>Wed, 19 Mar 2008 00:58:43 +0000</pubDate>
		<dc:creator>drasch</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[atlassian]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[jira]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[sprint]]></category>

		<guid isPermaLink="false">http://www.davidrasch.com/2008/03/18/atlassian-jira-and-confluence/</guid>
		<description><![CDATA[<p>We&#8217;ve started using Jira and Confluence as a replacement for Xplanner (which we used for almost 2 years). Jira&#8217;s an extremely flexible issue-tracking software product which allows us to track Bugs, Projects, Sprints, and even Ticket queues (like internal email support) all in one place. We hope to be able to relate issues to <span style="color:#777"> . . . &#8594; Read More: <a href="http://www.davidrasch.com/2008/03/18/atlassian-jira-and-confluence/">Atlassian Jira and Confluence</a></span>]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve started using <a href="http://www.atlassian.com/">Jira and Confluence</a> as a replacement for Xplanner (which we used for almost 2 years).  Jira&#8217;s an extremely flexible issue-tracking software product which allows us to track Bugs, Projects, Sprints, and even Ticket queues (like internal email support) all in one place.  We hope to be able to relate issues to one another and discover trends, bugs, and manage our software process more holistically.</p>
<p>The challenge has been defining the mapping between Jira&#8217;s entities and our business entities, mainly for managing the work in a given software sprint.</p>
<p>We&#8217;ve tried the following<br />
Sprint: Version<br />
Weekly Milestones: Due date<br />
Category of change: Component<br />
Type of task: Issue type<br />
High-level task: Issue<br />
Individual action in pursuit of high-level task: Sub-issue</p>
<p>This sprint we&#8217;re trying something different:<br />
Sprint: Project<br />
Weekly milestones: version<br />
High-level task: component<br />
Type of task: description<br />
Individual action&#8230;: Issue</p>
<p>Both have their pros and cons, what I&#8217;d love to know is how others solve this and whether they might have any advice on how they&#8217;ve configured the entities in Jira, use Links, etc to manage their Agile development projects.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.davidrasch.com/2008/03/18/atlassian-jira-and-confluence/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

