<?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>metrics Agile | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/metrics/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Wed, 28 May 2025 21:13:09 +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>metrics Agile | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Velocity is a Lagging Indicator</title>
		<link>https://www.scrumexpert.com/knowledge/velocity-is-a-lagging-indicator/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 03 Dec 2024 17:32:00 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Quotes]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<category><![CDATA[velocity Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8150</guid>

					<description><![CDATA[Velocity is one a key metrics used by Scrum teams to measure the rate at which an Agile team delivers value to the customer. In his book “Escape Velocity – Better Metrics for Agile Teams”, Doc Norton explains why velocity is not the ideal metric for Scrum teams. In this quote, he explains that Velocity is a lagging indicator. These metrics tend to be weak indicators for the short-term and are much more reliable for confirming long-term trends. Velocity is also a lagging indicator. It is a measure taken at the end of a series of steps. We plan, we prioritize, we work, we test, and then we measure. Lagging indicators are abstract Lagging indicators tend to be aggregate or abstract. They don’t provide detailed insight into the operations, rather they provide an indication of results. Net profit is a lagging indicator for a company. While it tells us about how the company is doing, it gives us no indication of why the organization was or was not successful. Let’s look at another lagging indicator; unemployment. The unemployment index is a lagging indicator. It tells us whether or not unemployment is on the rise or decline, which in turns tells us if the economy is doing poorly or well, respectively. An increase in unemployment means a sagging economy. A decrease in unemployment means a growing economy. But there is nothing about unemployment that tells us why the economy is performing in a particular manner or how we might go about <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/velocity-is-a-lagging-indicator/" title="Velocity is a Lagging Indicator">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Velocity is a Agile Measure of a Complex System</title>
		<link>https://www.scrumexpert.com/knowledge/velocity-is-a-agile-measure-of-a-complex-system/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 01 Aug 2024 16:39:33 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Quotes]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7946</guid>

					<description><![CDATA[Velocity is one of the key metrics used by Agile teams to measure the rate at which a team delivers value to the customer. In his book &#8220;Escape Velocity – Better Metrics for Agile Teams&#8221;, Doc Norton explains why velocity is not the ideal metric for Scrum teams. In this quote, he discusses the complexity of the system that underlies the velocity metric. This is ultimately quite significant. Velocity, while a simple concept, is actually a measure of output for a complex system. Think about the number of factors that go into a velocity measurement. There is the organizational mission, the broader business objectives, and the objective of the product itself. There are product owners, designers, architects, developers, testers, subject matter experts, security specialists, database specialists, governance, and production specialists involved. There are stand-ups, planning meetings, and retrospectives. There are epics, stories, and tasks all tracked on a board or in a system with multiple lanes representing different key states in the delivery of each single piece of work. After all these individuals interact with one another, responding to change, and collaborating with the customer in pursuit of working software, we take a single measurement. That single measurement represents the interactions of the individuals and all of their adaptions to change in the delivery of working software. Velocity is a simple measure of a very complex system. To measure creative work by throughput alone is to not measure it at all; quality and impact are essential. While a simple measure <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/velocity-is-a-agile-measure-of-a-complex-system/" title="Velocity is a Agile Measure of a Complex System">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Five Mistakes to Avoid When You Select Product Metrics</title>
		<link>https://www.scrumexpert.com/videos/five-mistakes-to-avoid-when-you-select-product-metrics/</link>
					<comments>https://www.scrumexpert.com/videos/five-mistakes-to-avoid-when-you-select-product-metrics/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 27 Nov 2023 17:17:20 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<category><![CDATA[product management]]></category>
		<category><![CDATA[product owner]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7711</guid>

					<description><![CDATA[Product metrics and key performance indicator(KPIs) have been getting increasingly more important and useful for Agile organizations that develop digital products. When done right, they can become an engine for product growth and inform great strategic and tactical decisions. When done wrong, they can lead to a huge amount of sunk resources and wasted time. This presentation explains the most common and the most dangerous mistakes that you should avoid to make sure your KPIs and metrics work to your advantage. You will learn to: * recognize the most typical problems with metrics in everyday work with your product * identify behaviors that lead to problems with metrics * prevent situations where a serious error is made when selecting product metrics https://vimeo.com/843391054 Video producer: https://aceconf.com/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/five-mistakes-to-avoid-when-you-select-product-metrics/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>How Agile Charts Lie</title>
		<link>https://www.scrumexpert.com/videos/how-agile-charts-lie/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 17 May 2023 15:18:50 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7516</guid>

					<description><![CDATA[In recent years, measurement has increasingly gained more traction in the Agile world. Many folks want to &#8220;measure&#8221; or even &#8220;measure what matters&#8221; when adopting new ways of working like Scrum. Whilst this enthusiasm is great, it is often channelled in the wrong way. This presentation demonstrates just how prevalent lying with Agile charts is, particularly with what will be some of your favorite metrics. The presenter also provides practical tips to improve the visualization and usage of data within your Scrum teams and Agile organization. Video producer: https://agilebyexample.com/ Further reading * Understanding the Scrum Burndown Chart * Agile Software Development Metrics &#038; KPIs for Teams * Lean Agile Metrics for Scaled Agile Systems * Metrics for agile projects: finding the right tools for the job]]></description>
		
		
		
			</item>
		<item>
		<title>Measuring Agile: Data to Grow your Scrum Team Agility</title>
		<link>https://www.scrumexpert.com/videos/measuring-agility-grow-your-team/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 04 Jul 2022 14:28:24 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7116</guid>

					<description><![CDATA[How do you know if your Scrum team is really Agile? Like predicting the weather, complex human systems need data analytics and statistical models over simple reporting, to understand what creates business agility from human behavior. This is the world of psychology, statistics, human behavior models. It is how medicine predicts if you have factors that predict heart attacks or if children are likely to have developmental delay. It is time to apply this to Agile teams to growing a true agile mindset. This talk looks at the psychology of human behavior and data analytics to provide a playbook for measuring and improve an agile mindset in Scrum teams to underpin true business agility. It looks at 10 years of longitudinal data, both from software and non-software agile teams, and large scale agile transformation initiatives, and the model that is now been produced to help coaches and the enterprise become more agile. Video producer: https://agileindia.org]]></description>
		
		
		
			</item>
		<item>
		<title>Measuring Outcomes: How to Get Meaningful Agile Metrics</title>
		<link>https://www.scrumexpert.com/videos/measuring-outcomes-how-to-get-meaningful-agile-metrics/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 30 Nov 2021 17:11:56 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[delivering value]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6827</guid>

					<description><![CDATA[&#8220;How well is your delivery team doing?&#8221; That seems like a straightforward question for an Agile team, but it is more complicated that it might sound at first. Do we know what it means to &#8220;do well&#8221; or is it one of those things that is different to everyone? This presentation discusses how you can meaningfully measure a team&#8217;s output and what you can learn from the measurements. It also explores common metrics pitfalls and provide insight in how to avoid them. You will learn to design metrics for your own purposes, and get started with some concrete examples to measure productivity of a delivery team. In short, you will have all the information to answer &#8220;how well your team is doing&#8221; meaningfully. Presentation slides: https://www.slideshare.net/ginomarckx/measuring-outcomes-or-how-to-get-meaningful-metrics Video producer: https://www.torontoagilecommunity.org/ Further reading: Lean Agile Metrics for Scaled Agile Systems]]></description>
		
		
		
			</item>
		<item>
		<title>Agile Software Development Metrics &#038; KPIs for Teams</title>
		<link>https://www.scrumexpert.com/knowledge/agile-software-development-metrics-kpis-for-teams/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 23 Aug 2021 15:05:48 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6742</guid>

					<description><![CDATA[From the perspective of Scrum, metrics and KPI evaluations are a few of the last frontiers in the process for continuous improvement. In this article, Lucas Napoli shares some metrics and KPIs that Agile software development teams should be aware of. Author: Lucas Napoli, Hexacta, https://www.hexacta.com/ From the methodology perspective, metric measures and KPI (Key Performance Indicators) evaluations are a few of the last frontiers in the process for continuous improvement. The values and charts that result from these practices help the client to make important decisions about the project, but also help the development team demonstrate the status of the situation. A couple of weeks before, we discussed those KPIs that are important for clients to take into account. With the aim of going a bit further and showing other important metrics within software projects, in this opportunity, I decided to focus on the KPIs the development industry should be aware of. Clients can also keep these in mind to see in detail if the outsourcing company is measuring the development properly. All participants in a project should be committed to these practices, and everyone needs to know the importance of reporting consumed hours, estimating effort, and other tasks that are not specifically related to software. In this article, we are going to enforce this idea, explaining the most commonly used metrics in Agile software development and their purpose. What are metrics and KPIs in software development To start with, it is important to clarify that one of the most common <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/agile-software-development-metrics-kpis-for-teams/" title="Agile Software Development Metrics &#038; KPIs for Teams">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Customer KPIs in Agile Software Development</title>
		<link>https://www.scrumexpert.com/knowledge/customer-kpis-in-agile-software-development/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 16 Mar 2020 15:53:42 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[delivering value]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6195</guid>

					<description><![CDATA[Metrics are an important part of the Agile software development approaches like Scrum. They are however, like velocity, more often focus on the performance of the delivery team. What about the customers? In this article, Fabio Gasparri discusses Key Performance Indicators (KPIs) that will matter for the clients. Author: Fabio Gasparri, Senior Partner at Hexacta, https://www.hexacta.com/ Agile performance is difficult to measure. Even seasoned development teams struggle to set the right markers of performance and track them effectively. Find out how to face this challenge. We live in the era of digital and whether you are updating a legacy enterprise system or creating a customer-facing app, product development is crucial to business success. It is true virtually everywhere you go, from e-commerce to healthcare to utilities to government and everything in between. But while it is established that digital products are essential for doing business in the 21st century, what is not established is how you measure progress when you are working on developing these products together with an outsourcing company. The software development process has undergone a dramatic overhaul during the last few decades, with Agile methodologies swiftly rising in popularity especially in the last decade. In case you are unfamiliar with Agile, here is a quick definition: an iterative process of development that focuses on continuous short cycles of stakeholder feedback followed by a collaborative team response to that feedback. The product is never really “finished” but is rather considered to be in a continual state of improvement. <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/customer-kpis-in-agile-software-development/" title="Customer KPIs in Agile Software Development">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Evidence Based Management</title>
		<link>https://www.scrumexpert.com/videos/evidence-based-management/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 28 Jan 2020 16:19:57 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6125</guid>

					<description><![CDATA[Organizations invest in agile processes, tools, training, and coaching, but how much are they getting back? Has product delivery improved? How much happier are users and the business customers? Are employees empowered and enabled? Traditional metrics might give you insight into improvements of operational efficiency, but the real conversation is about the value created for your organization by the improved processes. Without measuring value, the success of any agile initiative is based on nothing more than intuition and assumption. Evidence-Based Management (EBM) is a framework to help measure, manage, and increase the value derived from product delivery. EBM focuses on improving outcomes, reducing risks, and optimizing investments and is an important tool to help leaders put the right measures in place to invest in the right places, make smarter decisions and reduce risk using an iterative and incremental approach. This empirical method alongside the agile principles and values of Scrum enables successful steps of change for the organization. Mia will discuss Evidence based management and how this empirical process can help agile transformations measure and manage the value derived from the transformation initiative. Mia will focus on the 4 Key Value Areas: Current Value, Ability to Innovate, Unrealized Value and time to market and how these contribute to an organization’s ability to deliver business value. Video producer: http://agileindia.org]]></description>
		
		
		
			</item>
		<item>
		<title>Escape Velocity</title>
		<link>https://www.scrumexpert.com/knowledge/escape-velocity/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 05 Aug 2019 14:28:17 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[metrics Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=5908</guid>

					<description><![CDATA[Following the famous mantra of “you can&#8217;t manage what you can&#8217;t measure”, Scrum teams have often a set of metrics to monitor their activity. Velocity, the amount of work performed by a team during a single sprint, might be one of the most famous Agile metric. Doc Norton has written an interesting book about the negative sides of velocity and what might be a good metric for an Agile team. Based on his experience, Doc Norton starts his book with a long discussion of the flaws of the velocity metric. From this base, he explains then the issues with metrics in general and proposes alternative measures (lead time, team joy, etc.) to monitor the evolution of Agile teams. My favorite part is the section that tries to examine the problem from a customer perspective. This book is easy to read, mixing concepts with stories from the trenches. I will recommend this book naturally to every member of a Scrum team, but it should provide interesting ideas to every software development project manager or executive. Reference: Escape Velocity &#8211; Better Metrics for Agile Teams, Doc Norton, https://leanpub.com/escapevelocity Quotes Velocity is a poor metric that offers far less value than the angst that results from the perpetual misuse. In agile software development, velocity is the rate at which a team delivers value to the customer. Value is quantifiable, and we can therefore say it has size. The direction is indicated by the traversal from idea to implementation. A team that completes lots <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/escape-velocity/" title="Escape Velocity">[...]</a>]]></description>
		
		
		
			</item>
	</channel>
</rss>
