<?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>tracking | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/tracking/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Mon, 14 Apr 2014 18:49:21 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.scrumexpert.com/wp-content/uploads/favicon.png</url>
	<title>tracking | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Feature Board and Cards</title>
		<link>https://www.scrumexpert.com/knowledge/feature-board-and-cards/</link>
					<comments>https://www.scrumexpert.com/knowledge/feature-board-and-cards/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 14 Apr 2014 18:46:52 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1922</guid>

					<description><![CDATA[Most of the Scrum teams use a task board to visualize their activity and progress with task cards. In these two blog posts, Keith Clinton, the author of Agile Game Development with Scrum, discusses the concept of feature boards and feature cards. Task cards contain information about individual tasks that will be needed to complete a set of features. Keith Clinton says that the problem of task boards is the lack of visibility of cross-discipline dependencies. In a feature board, cards move around the board depending on the work that is being done. The feature card contains the following elements : title, description, acceptance criteria, estimates and tasks. There are three benefits of feature boards over traditional Scrum task board: * feature boards focus the team on completing prioritized features over merely completing tasks in any particular order. * feature boards help balance cross-discipline teams. * feature boards help limit Work-in-Progress (WiP). The conclusion is that &#8220;Feature Boards fit best within a time-boxed iteration which has a lot of “swarming”. “Swarming” means that there is an unpredictable flow of work between disciplines to create a feature and the feature will bounce around or iterate unpredictably before the fun is discovered.&#8221; Read these two complete blog posts about feature board and feature rards on http://blog.agilegamedevelopment.com/2014/04/feature-boards.html and http://blog.agilegamedevelopment.com/2014/04/feature-cards.html.]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/feature-board-and-cards/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Assess your Scrum Project Status with the Cumulative Flow Diagram</title>
		<link>https://www.scrumexpert.com/knowledge/assess-your-scrum-project-status-with-the-cumulative-flow-diagram/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 30 Jul 2013 17:06:58 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1596</guid>

					<description><![CDATA[The Cumulative Flow Diagram (CFD) provides typical information about status of your Scrum project: how much work is done, ongoing and in backlog, what is the pace of progress, etc. In this blog post, Pawel Brodzinski explains that you can also use the Cumulative Flow Diagram to detect the issues that a Scrum team might face. The Cumulative Flow Diagram allows to detect the changes of scope and the work in progress. The blog post explores several typical cases of Cumulative Flow Diagram and explains what might be the problem that cause the lines in the diagram differ from a &#8220;normal&#8221; case. This post provides many varieties of Cumulative Flow Diagram and gives for each of them some hints on how they could help you diagnostic issues with your project. Read the complete post on http://brodzinski.com/2013/07/cumulative-flow-diagram.html]]></description>
		
		
		
			</item>
		<item>
		<title>Scrum Big Picture</title>
		<link>https://www.scrumexpert.com/knowledge/scrum-big-picture/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 07 Jan 2013 15:38:20 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[burndown chart]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1344</guid>

					<description><![CDATA[How can you share information about a Scrum project between the team members or assess its status? This article by Kulawat Wongsaroj proposes eight visualizations techniques to share information on a Scrum project. All these techniques try to summarize the large and complex set of data of a Agile project in different dimensions. They exist to help the ScrumMaster, the other team members and the other various stakeholders like managers to get a better understanding of the project. These eight visual techniques are: * (Release) Burndown Chart * Story Mapping * Parking Lot * Scaled Bar Chart * Treemap * Dartboard * Stacked Area Chart * Burndown and Epic Bar For each technique, the article provides an example and some explanations about what information they display. At the end of the article, a table allow to compare the different techniques with their benefits and disadvantages.]]></description>
		
		
		
			</item>
		<item>
		<title>Learning to Fail in Scrum</title>
		<link>https://www.scrumexpert.com/knowledge/learning-to-fail-in-scrum/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 06 Oct 2011 16:34:25 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=745</guid>

					<description><![CDATA[This article explains that it is important to end doomed projects before they become “too big to fail”. This article isn&#8217;t about the personal benefits of failure, but is rather about Agile software development. It&#8217;s about how failure, recognizing it and doing something about it, is a critical element of any Agile initiative.]]></description>
		
		
		
			</item>
		<item>
		<title>Comparing Scrum and Kanban Tracking Boards</title>
		<link>https://www.scrumexpert.com/knowledge/comparing-scrum-and-kanban-tracking-boards/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 24 Aug 2011 19:36:01 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[kanban]]></category>
		<category><![CDATA[lean]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=666</guid>

					<description><![CDATA[In this blog post, Ken Pugh compares the usage of Kanban board and Scrum tracking boards to track progress of agile projects. He concludes that Scrum-style boards and Kanban-style boards can provide the same information, but in different ways.]]></description>
		
		
		
			</item>
		<item>
		<title>Dashboards for Scrum Projects</title>
		<link>https://www.scrumexpert.com/knowledge/dashboards-for-scrum-projects/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 13 Jul 2011 17:46:33 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[product owner]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=583</guid>

					<description><![CDATA[This article aims to bring to the table a consolidated Scrum Project Dashboard layout that could be easily maintained and updated by the Product Owner with day-to-day and well-known information provided by the team. He will be able to get stakeholder and management attention and support while providing an updated clear picture on the Project’s status.]]></description>
		
		
		
			</item>
		<item>
		<title>Measuring Scrum Sprints Progress</title>
		<link>https://www.scrumexpert.com/knowledge/measuring-scrum-sprints-progress/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 26 May 2011 17:47:50 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[sprint]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=534</guid>

					<description><![CDATA[Martín Alaimo proposes to measure Scrum sprint progress with a continually updated ETC (estimate-to-complete) for each user story.]]></description>
		
		
		
			</item>
		<item>
		<title>Create a Burndown Chart in Google Docs</title>
		<link>https://www.scrumexpert.com/knowledge/create-a-burndown-chart-in-google-docs/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 10 May 2011 20:05:50 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[burndown chart]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=518</guid>

					<description><![CDATA[A simple tutorial on how to create a Scrum Burndown Chart with Google Docs for free.]]></description>
		
		
		
			</item>
		<item>
		<title>Managing Schedule Flaws Using Agile Methods</title>
		<link>https://www.scrumexpert.com/knowledge/managing-schedule-flaws-using-agile-methods/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 26 Apr 2011 13:50:58 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[tracking]]></category>
		<category><![CDATA[velocity Agile]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=486</guid>

					<description><![CDATA[This article discusses several symptoms and causes of schedule flaws, presents metrics and diagrams that can be used to track your team’s progress against its schedule and describes how Agile can address project management risks.]]></description>
		
		
		
			</item>
		<item>
		<title>Managing Risk on Agile Projects with the Risk Burndown Chart</title>
		<link>https://www.scrumexpert.com/knowledge/managing-risk-on-agile-projects-with-the-risk-burndown-chart/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 08 Apr 2010 21:16:30 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[tracking]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=231</guid>

					<description><![CDATA[Risk management is a central part of traditional project management and is included as one of the knowledge areas in the Project Management Institute’s (PMI) body of knowledge. In many of my classes, participants ask how Scrum and agile address risk management. Some are concerned that agile or Scrum ignore risk management completely. This post explains how to manage risk on agile projects with the risk burndown chart.]]></description>
		
		
		
			</item>
	</channel>
</rss>
