<?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>burndown chart | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/burndown-chart/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Wed, 06 Jan 2016 16:38:23 +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>burndown chart | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Failing Scrum Metrics Programs</title>
		<link>https://www.scrumexpert.com/knowledge/failing-scrum-metrics-programs/</link>
					<comments>https://www.scrumexpert.com/knowledge/failing-scrum-metrics-programs/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 03 Nov 2015 15:05:22 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Quotes]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[burndown chart]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<category><![CDATA[velocity Agile]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2920</guid>

					<description><![CDATA[Even if Agile was initially considered as an anarchic approach due to practices like self-organization, the reality is that it requires a lot of discipline. Metrics is an important tool to assess the continuous improvement efforts of Scrum teams. However, setting a good metric program is not obvious. The book &#8220;The Agile Culture&#8221; contains interesting thoughts about what could make a metrics program fail. Many metrics programs fail and many more do not achieve their intended goals. There are many reasons for this but some of the most common are * Unclear goals and vision of what the organization is trying to achieve. * Misuse of metrics for competitive comparisons or as a punishment rather than a learning process. * Using metrics for political or other purposes rather than using them to help people to do their jobs more effectively and to deliver more value. * Poor communication of the goals and intentions of the program to those involved. * Focusing on process and not results. * Too many metrics leading to lack of focus and ineffectiveness. * Measuring vanity metrics. * Measurements are not timely or the action cycle time is too long. * Poor leadership, which is focused on the metrics process rather than its goals and effect. * Not adapting to the changing needs of the business. Metrics will change over time and you need a mechanism to ensure they remain relevant and effective. If you must have an organizational metrics program, then focus on using it <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/failing-scrum-metrics-programs/" title="Failing Scrum Metrics Programs">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/failing-scrum-metrics-programs/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</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>Scrum Burnup and Burndown Charts</title>
		<link>https://www.scrumexpert.com/knowledge/scrum-burnup-and-burndown-charts/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 07 Mar 2012 18:34:47 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[burndown chart]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=986</guid>

					<description><![CDATA[Burn charts are a simple method to monitor work progress in Scrum. This article discusses the details of burn down and burn up charts: which units to measure, how to adapt to scope variations. He gives some guidelines on how to interpret burndown charts. He reminds that the chart should be objective and visible.]]></description>
		
		
		
			</item>
		<item>
		<title>Understanding the Scrum Burndown Chart</title>
		<link>https://www.scrumexpert.com/knowledge/understanding-the-scrum-burndown-chart/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 06 Feb 2012 15:43:45 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[burndown chart]]></category>
		<category><![CDATA[velocity Agile]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=912</guid>

					<description><![CDATA[The Scrum Burndown chart is very simple tool to monitor the project status. It is easy to explain, easy to understand. But this metric also put in evidence some pitfalls observed in many agile workshops and adoptions. This article discusses how to build a Scrum burndown chart and what should be included in it. It also presents guidelines on how to assess the project status using the burndown chart and what could be done when problems are detected.]]></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>
	</channel>
</rss>
