<?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: Project Management with Scrum</title>
	<atom:link href="http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/</link>
	<description>Agile, Scrum, Bug tracking, Programming, business of software, and Marketing</description>
	<lastBuildDate>Mon, 26 Mar 2012 11:50:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: LDAdams</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-929</link>
		<dc:creator>LDAdams</dc:creator>
		<pubDate>Thu, 05 Mar 2009 15:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-929</guid>
		<description>What features of the new 2009 version are left out in Express 5 for $5 regarding features particular to scrum.

Thanks,
Luke</description>
		<content:encoded><![CDATA[<p>What features of the new 2009 version are left out in Express 5 for $5 regarding features particular to scrum.</p>
<p>Thanks,<br />
Luke</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Ferry</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-928</link>
		<dc:creator>Matthew Ferry</dc:creator>
		<pubDate>Sat, 04 Oct 2008 00:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-928</guid>
		<description>We&#039;d be a good size customer. The &lt;b&gt;only&lt;/b&gt; reason we haven&#039;t bought OnTime is that it doesn&#039;t have direct support for Scrum (meaning burn down tracking, etc). But if you deliver on what you are saying many firms, like ours, will flock.</description>
		<content:encoded><![CDATA[<p>We&#8217;d be a good size customer. The <b>only</b> reason we haven&#8217;t bought OnTime is that it doesn&#8217;t have direct support for Scrum (meaning burn down tracking, etc). But if you deliver on what you are saying many firms, like ours, will flock.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-927</link>
		<dc:creator>Ross</dc:creator>
		<pubDate>Fri, 03 Oct 2008 10:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-927</guid>
		<description>This is the first time I have seen on Time. I will definitely be checking it out but good support for Scrum is definitely a must.</description>
		<content:encoded><![CDATA[<p>This is the first time I have seen on Time. I will definitely be checking it out but good support for Scrum is definitely a must.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MW</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-926</link>
		<dc:creator>MW</dc:creator>
		<pubDate>Wed, 10 Sep 2008 18:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-926</guid>
		<description>This is great news, we are currently an Axosoft customer using OnTime to manage our projects and we have struggled (successfully) to impliment our Scrum methodology into the OnTime software.  We stuck it out because OnTime has many additional features that work well on top of Scrum ie Customer Portal, reporting, a slick client.  One thing that would be extremely useful for us is an integration with Team Foundation Server so that developers can work out of the Team Explorer and have their modifications show up in OnTime for review by our PM team.  This would be huge!!!  In any case, we look forward to this release!</description>
		<content:encoded><![CDATA[<p>This is great news, we are currently an Axosoft customer using OnTime to manage our projects and we have struggled (successfully) to impliment our Scrum methodology into the OnTime software.  We stuck it out because OnTime has many additional features that work well on top of Scrum ie Customer Portal, reporting, a slick client.  One thing that would be extremely useful for us is an integration with Team Foundation Server so that developers can work out of the Team Explorer and have their modifications show up in OnTime for review by our PM team.  This would be huge!!!  In any case, we look forward to this release!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrej</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-925</link>
		<dc:creator>Andrej</dc:creator>
		<pubDate>Fri, 05 Sep 2008 09:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-925</guid>
		<description>It is great to hear you are working on support for Scrum in OnTime. We are using Scrum process, and here is our way of organizing Sprints: we use Features as the Project Backlog. During the Sprint planning meeting, we break features into smaller tasks (maybe just two, maybe sometimes more to easier estimate the feature cost), assigned to the developer and tester that will work in the story. We use OnTime worklog, which tracks the amount of work done for each task. 

All this information is processed by a small application, that we created using OnTime SDK - from the features, tasks (and its status) and worklog entries we also get the burndown information (historical). The application also prints the story cards, that we track on the whiteboard (New, InProgress, Done) during daily standup meetings. 

Looking forward to see Scrum support in V9!</description>
		<content:encoded><![CDATA[<p>It is great to hear you are working on support for Scrum in OnTime. We are using Scrum process, and here is our way of organizing Sprints: we use Features as the Project Backlog. During the Sprint planning meeting, we break features into smaller tasks (maybe just two, maybe sometimes more to easier estimate the feature cost), assigned to the developer and tester that will work in the story. We use OnTime worklog, which tracks the amount of work done for each task. </p>
<p>All this information is processed by a small application, that we created using OnTime SDK &#8211; from the features, tasks (and its status) and worklog entries we also get the burndown information (historical). The application also prints the story cards, that we track on the whiteboard (New, InProgress, Done) during daily standup meetings. </p>
<p>Looking forward to see Scrum support in V9!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HL Arledge</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-924</link>
		<dc:creator>HL Arledge</dc:creator>
		<pubDate>Tue, 02 Sep 2008 20:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-924</guid>
		<description>Hamid, I have volunteered to assist your QA team, and I am excited about seeing what your team puts together in the coming year, but I do have an interest in preserving my historical data somehow. Thanks again!

Ted, a reminder in case you have not heard it said: Scrum is NOT a development methodology. It is a management methodology, and it is so easy that even managers can grasp it quickly (grinning). This makes Scrum the perfect choice for teams like yours. You can see progress with Scrum in mere weeks WITHOUT paying any consultants. At its heart, Scrum is nothing more than using common sense to management a project.</description>
		<content:encoded><![CDATA[<p>Hamid, I have volunteered to assist your QA team, and I am excited about seeing what your team puts together in the coming year, but I do have an interest in preserving my historical data somehow. Thanks again!</p>
<p>Ted, a reminder in case you have not heard it said: Scrum is NOT a development methodology. It is a management methodology, and it is so easy that even managers can grasp it quickly (grinning). This makes Scrum the perfect choice for teams like yours. You can see progress with Scrum in mere weeks WITHOUT paying any consultants. At its heart, Scrum is nothing more than using common sense to management a project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-923</link>
		<dc:creator>Ted</dc:creator>
		<pubDate>Mon, 01 Sep 2008 01:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-923</guid>
		<description>Also stats of methods that Ontime users use don&#039;t backup the fact that ad-hoc wins. it is simply that customers who don&#039;t have any methodology (like us) find it easier to use tools like Ontime (flexible and easy to use). I am sure customer who do have strict methodologies and even Agile ones would use other tools that are more tailored for it, and therefore will not be Axosoft customer. I am quite excited that Ontime is going to introduce SCRUM and I am sure once this is done, and the same survey published in 12 months time, stats will look different.
Regards.</description>
		<content:encoded><![CDATA[<p>Also stats of methods that Ontime users use don&#8217;t backup the fact that ad-hoc wins. it is simply that customers who don&#8217;t have any methodology (like us) find it easier to use tools like Ontime (flexible and easy to use). I am sure customer who do have strict methodologies and even Agile ones would use other tools that are more tailored for it, and therefore will not be Axosoft customer. I am quite excited that Ontime is going to introduce SCRUM and I am sure once this is done, and the same survey published in 12 months time, stats will look different.<br />
Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamid Shojaee</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-922</link>
		<dc:creator>Hamid Shojaee</dc:creator>
		<pubDate>Fri, 29 Aug 2008 20:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-922</guid>
		<description>HL, thanks for your comment. Yes, it&#039;s also possible to organize sprints as project folders. In 2009, we&#039;ll have a different way to organize Sprints (or more generally, milestones). I&#039;ll be talking about that later this year.</description>
		<content:encoded><![CDATA[<p>HL, thanks for your comment. Yes, it&#8217;s also possible to organize sprints as project folders. In 2009, we&#8217;ll have a different way to organize Sprints (or more generally, milestones). I&#8217;ll be talking about that later this year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HL Arledge</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-921</link>
		<dc:creator>HL Arledge</dc:creator>
		<pubDate>Fri, 29 Aug 2008 19:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-921</guid>
		<description>Hamid

My Scrum team has been using OnTime for over a year successfully. We had to use Microsoft Reporting Services and some custom fields and database triggers to meet the Burndown short-comings you&#039;ve described, but generally the OnTime works well with Scrum.

However, what works for us is slightly different than your proposal. Product Backlog Items map well to what OnTime natively labels &quot;Features&quot;, and the Sprint Backlog maps perfectly to what OnTime natively labels &quot;Tasks&quot;. We use folder (OnTime&#039;s &quot;Projects&quot;) to manage sprints. This provides us with the flexibility you described regarding drop-downs, but without losing the Project Management folders that work so well in OnTime today.

The only additional feature we are missing relates to the fact that the Sprint Backlog (Tasks) is not available in the OnTime Customer Portal. This is critical to maintain the visibility you mentioned between our team and our stakeholders.

Thanks,
HL</description>
		<content:encoded><![CDATA[<p>Hamid</p>
<p>My Scrum team has been using OnTime for over a year successfully. We had to use Microsoft Reporting Services and some custom fields and database triggers to meet the Burndown short-comings you&#8217;ve described, but generally the OnTime works well with Scrum.</p>
<p>However, what works for us is slightly different than your proposal. Product Backlog Items map well to what OnTime natively labels &#8220;Features&#8221;, and the Sprint Backlog maps perfectly to what OnTime natively labels &#8220;Tasks&#8221;. We use folder (OnTime&#8217;s &#8220;Projects&#8221;) to manage sprints. This provides us with the flexibility you described regarding drop-downs, but without losing the Project Management folders that work so well in OnTime today.</p>
<p>The only additional feature we are missing relates to the fact that the Sprint Backlog (Tasks) is not available in the OnTime Customer Portal. This is critical to maintain the visibility you mentioned between our team and our stakeholders.</p>
<p>Thanks,<br />
HL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://www.axosoft.com/blog/2008/08/28/project-managemen-with-scrum/#comment-920</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Fri, 29 Aug 2008 02:55:18 +0000</pubDate>
		<guid isPermaLink="false">http://shipsoftware.wordpress.com/?p=190#comment-920</guid>
		<description>I haven&#039;t heard of OnTime before. Will definitely check it.

Excellent article btw.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t heard of OnTime before. Will definitely check it.</p>
<p>Excellent article btw.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

