<?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: GQM: Metrics come last</title> <atom:link href="http://www.dtsato.com/blog/2010/01/06/gqm-metrics-come-last/feed/" rel="self" type="application/rss+xml" /><link>http://www.dtsato.com/blog/2010/01/06/gqm-metrics-come-last/</link> <description>We can change!</description> <lastBuildDate>Wed, 07 May 2014 20:15:42 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>https://wordpress.org/?v=4.2.39</generator> <item><title>By: Danilo Sato</title><link>http://www.dtsato.com/blog/2010/01/06/gqm-metrics-come-last/comment-page-1/#comment-19587</link> <dc:creator><![CDATA[Danilo Sato]]></dc:creator> <pubDate>Thu, 07 Jan 2010 17:25:18 +0000</pubDate> <guid
isPermaLink="false">http://www.dtsato.com/blog/?p=354#comment-19587</guid> <description><![CDATA[Mark,
There&#039;s usually two ways to look at software quality: intrinsic quality and extrinsic quality. Intrinsic is what makes sure the software runs as expected (performance metrics, test coverage, how long it takes to deploy, code complexity, size, etc.). Extrinsic is what makes sure it&#039;s fit for purpose, which is a lot harder to measure. It&#039;s usually from the point of view of the customer (are people using it? how many complaints? are people paying for it?)
But, as you said, this leaves out a lot of quality attributes that should be managed but can&#039;t be measured, like: usability, gameplay (if you&#039;re building games), customer satisfaction, team/employee satisfaction, ...
Regards,
Danilo]]></description> <content:encoded><![CDATA[<p>Mark,</p><p>There&#8217;s usually two ways to look at software quality: intrinsic quality and extrinsic quality. Intrinsic is what makes sure the software runs as expected (performance metrics, test coverage, how long it takes to deploy, code complexity, size, etc.). Extrinsic is what makes sure it&#8217;s fit for purpose, which is a lot harder to measure. It&#8217;s usually from the point of view of the customer (are people using it? how many complaints? are people paying for it?)</p><p>But, as you said, this leaves out a lot of quality attributes that should be managed but can&#8217;t be measured, like: usability, gameplay (if you&#8217;re building games), customer satisfaction, team/employee satisfaction, &#8230;</p><p>Regards,<br
/> Danilo</p> ]]></content:encoded> </item> <item><title>By: Mark Graban</title><link>http://www.dtsato.com/blog/2010/01/06/gqm-metrics-come-last/comment-page-1/#comment-19533</link> <dc:creator><![CDATA[Mark Graban]]></dc:creator> <pubDate>Wed, 06 Jan 2010 12:53:17 +0000</pubDate> <guid
isPermaLink="false">http://www.dtsato.com/blog/?p=354#comment-19533</guid> <description><![CDATA[Thanks for the link. As someone who is not a developer, I have a question about how you measure code &quot;quality.&quot; Number of bugs and number of defects would seem to not go far enough. How do you measure fitness for use? Seems like a lot of that would be subjective, but it has to be managed anyway, correct?
Can you share an example of something you manage, but cannot be measured?
You&#039;re right that the things that are easy to measure often aren&#039;t the important things.
mark]]></description> <content:encoded><![CDATA[<p>Thanks for the link. As someone who is not a developer, I have a question about how you measure code &#8220;quality.&#8221; Number of bugs and number of defects would seem to not go far enough. How do you measure fitness for use? Seems like a lot of that would be subjective, but it has to be managed anyway, correct?</p><p>Can you share an example of something you manage, but cannot be measured?</p><p>You&#8217;re right that the things that are easy to measure often aren&#8217;t the important things.</p><p>mark</p> ]]></content:encoded> </item> </channel> </rss>