<?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>Thomas Murphy &#187; Metrics</title>
	<atom:link href="http://blogs.gartner.com/tom_murphy/category/metrics/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/tom_murphy</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Tue, 31 Jan 2012 20:22:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Metrics, The Trap We All Fall Into</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/06/08/metrics-the-trap-we-all-fall-into/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/06/08/metrics-the-trap-we-all-fall-into/#comments</comments>
		<pubDate>Tue, 08 Jun 2010 16:06:17 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Metrics]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/06/08/metrics-the-trap-we-all-fall-into/</guid>
		<description><![CDATA[A lot of the calls I take focus on metrics for the QA team.&#160; How many testers per developer, how many hours of testing, how many defects, etc.&#160; Unfortunately many of these metrics don&#8217;t end up yielding useful information often because they are too simple and they leave to many variables open.&#160; We like metrics [...]]]></description>
			<content:encoded><![CDATA[<p>A lot of the calls I take focus on metrics for the QA team.&#160; How many testers per developer, how many hours of testing, how many defects, etc.&#160; Unfortunately many of these metrics don&#8217;t end up yielding useful information often because they are too simple and they leave to many variables open.&#160; We like metrics because they can help us get a read on project directions and if we are falling in the averages or not but it is too easy to fall into the trap of easy metrics that mislead.&#160; I discussed this in earlier research on defect containment (see Toolkit: Defect Containment and Quantitative Defect Management, G00160257).&#160; Yesterday at IBM&#8217;s Innovate conference <a href="http://www.ivarjacobson.com/home.cfm">Ivar Jacobson</a> talked about the need to focus on metrics that were better not easy:    <br /><i></i></p>
<blockquote><p><i>People look at the wrong things:         <br />– Things that are easy to measure but meaningless          <br />– “Checking boxes” rather than results          <br />– Few, if any, qualitative measures          <br />And present them in the wrong way:          <br />– Confusing and contradictory data          <br />– Meaningful only to specialists &#8211; and maybe not even to them!          <br />– Unclear purpose          <br />– Point data and not trends          <br />– Hard to understand and use to make decisions          <br />To close the gap, how well you are doing needs to be measured in business terms</i></p>
</blockquote>
<p> <i>
<p></p>
<p>   </i>He suggested looking at metrics that help see if we are delivering better applications, delivering faster, systems that are easier to use, cheaper to run, and leading to happier users.&#160; These are not single dimension views but they focus on what matters.&#160; IBM is adding a number of capabilities for improved metrics to its Team Concert ALM product (as are other ALM vendors) and while these tools do provide increased reporting capabilities it will be important to not misuse the information and to recognize that seeing bad numbers doesn&#8217;t mean seeing &quot;bad people&quot;.&#160; This is the real core of the use of metrics is while they may be the proverbial warning flag they don&#8217;t tell you directly how to fix the problem.&#160; This doesn&#8217;t mean all dashboards are evil but they can&#8217;t replace Management by Walking Around and getting your hands dirty.
<p><img alt="" src="http://img.zemanta.com/pixy.gif?x-id=3cab1968-5afe-8edb-a01e-fd9197ccf136" /></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/06/08/metrics-the-trap-we-all-fall-into/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test COE == ROI?</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/04/04/test-coe-roi/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/04/04/test-coe-roi/#comments</comments>
		<pubDate>Sun, 04 Apr 2010 04:12:37 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[Metrics]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[COE]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/04/04/test-coe-roi/</guid>
		<description><![CDATA[A common question currently is something along these lines: &#8220;If we shift to a Testing COE, what will be the ROI?&#8221;&#160; This is understandable given two primary related drivers: Testing is often seen as a bottleneck and a desire to drive overall AD efficiency.&#160; The challenge is that any ROI will be dependent on the [...]]]></description>
			<content:encoded><![CDATA[<p>A common question currently is something along these lines: &#8220;If we shift to a Testing COE, what will be the ROI?&#8221;&nbsp; This is understandable given two primary related drivers: Testing is often seen as a bottleneck and a desire to drive overall AD efficiency.&nbsp; The challenge is that any ROI will be dependent on the initial state and while there are some elements of a COE or centralizing the QA group that may provide an improvement to efficiency most of the improvements are not going to come from the organization structure but from practices and changes to behavior.&nbsp; If QA is a bottleneck because &#8220;they are always finding bugs late in the project&#8221; they are just doing their job.&nbsp; If those bugs are really requirements defects a Testing COE won&#8217;t help.&nbsp; We will publish more on this as we build out the research around this year&#8217;s MQ update as there are a lot of practical steps that can be taken to drive productivity and there are places where a central resource can be very useful, but it can&#8217;t be boiled down to a simple calculation.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/04/04/test-coe-roi/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Welcome</title>
		<link>http://blogs.gartner.com/tom_murphy/2008/09/16/welcome/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2008/09/16/welcome/#comments</comments>
		<pubDate>Tue, 16 Sep 2008 06:06:20 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[ALM]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[MarketScope]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/?p=3</guid>
		<description><![CDATA[I will use this space to point to interesting new developments and research in the software quality assurance and testing area as well as covering general AD and Agile topics.  We have a lot of great new research underway including a MarketScope for ALM.  ALM has been a hot topic for several years now and [...]]]></description>
			<content:encoded><![CDATA[<p>I will use this space to point to interesting new developments and research in the software quality assurance and testing area as well as covering general AD and Agile topics.  We have a lot of great new research underway including a MarketScope for ALM.  ALM has been a hot topic for several years now and the market is slowly begining to take shape evolving from vendors buying and buildling huge suites of management and task oriented tools (e.g. Test Case Managment and Automated Functioal Testing) to focus on the overall governance of delivering software and aiding cross functional collaboration.  Much of the evolution has fit together with the general shift toward Agile practices and current tools have good support for these and also provide the required balance of management reporting combined with team member agility.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2008/09/16/welcome/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

