<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Positioning Code Metrics to Management</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/28/positioning-code-metrics-to-management.aspx</link><description>Another question that is coming up is: How can (or should) code metrics be presented to management ? My view is that in all cases the metrics are something that can help make decisions around focus and prioritization. Management should be made aware of</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; Positioning Code Metrics to Management</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/28/positioning-code-metrics-to-management.aspx#6587527</link><pubDate>Thu, 29 Nov 2007 03:07:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6587527</guid><dc:creator>MSDN Blog Postings  » Positioning Code Metrics to Management</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/11/28/positioning-code-metrics-to-management/"&gt;http://msdnrss.thecoderblogs.com/2007/11/28/positioning-code-metrics-to-management/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Positioning Code Metrics to Management</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/28/positioning-code-metrics-to-management.aspx#6599570</link><pubDate>Thu, 29 Nov 2007 18:08:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6599570</guid><dc:creator>Joe</dc:creator><description>&lt;p&gt;I'd keep metrics away from non-technical management. &amp;nbsp;The last thing anyone wants is for the metrics to be used as absolute targets as opposed to guidance.&lt;/p&gt;
</description></item><item><title>VSTS Links - 12/03/2007</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/28/positioning-code-metrics-to-management.aspx#6646128</link><pubDate>Mon, 03 Dec 2007 18:20:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6646128</guid><dc:creator>Team System News</dc:creator><description>&lt;p&gt;Brian Harry on Update #2 on Installation Questions. Steven St. Jean on VSTS Web Test Tidbit - Testing...&lt;/p&gt;
</description></item><item><title>re: Positioning Code Metrics to Management</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/28/positioning-code-metrics-to-management.aspx#6729625</link><pubDate>Tue, 11 Dec 2007 04:47:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6729625</guid><dc:creator>conorm</dc:creator><description>&lt;p&gt;Joe raises a key point: the last thing anyone wants is for metrics to be used as absolute targets. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;I totally agree with this but even non-technical management should appreciate if you are able to back up your business decisions with some data that could be based around these code metrics.&lt;/p&gt;
</description></item><item><title>re: Positioning Code Metrics to Management</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/28/positioning-code-metrics-to-management.aspx#7514344</link><pubDate>Thu, 07 Feb 2008 15:24:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7514344</guid><dc:creator>Oded Gil</dc:creator><description>&lt;p&gt;I don't use code matrices yet (vs2003) but, I use probability X impact to measure the risk. &lt;/p&gt;
&lt;p&gt;For example, if most of the code (let's say 80%) is not readable. the probability to spent time to understand the code is 4 out of 5 and the impact is, let's say, 2 out of 5 because after a few hours of line by line debugging the problem can be solved. The risk is 2X5=10&lt;/p&gt;
&lt;p&gt;Same way we do for performance, exception management, logging... &lt;/p&gt;
&lt;p&gt;This way I can present a nice graph showing the risk to the management, they can see the risk with the highest bar and make a decision to spent time and fix it.&lt;/p&gt;
&lt;p&gt;The idea was not mine, a consultant from Microsoft Israel thought about it first.&lt;/p&gt;
</description></item><item><title>Visual Studio Team System 2008 Development Edition with MSDN Premium Subscription</title><link>http://blogs.msdn.com/fxcop/archive/2007/11/28/positioning-code-metrics-to-management.aspx#9399229</link><pubDate>Thu, 05 Feb 2009 20:33:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9399229</guid><dc:creator>Termékinformációk fejlesztőknek</dc:creator><description>&lt;p&gt;[ Nacsa S&amp;#225;ndor , 2009. janu&amp;#225;r 19. – febru&amp;#225;r 5.] Ez a Team System v&amp;#225;ltozat fejlett eszk&amp;#246;zrendszert k&amp;#237;n&amp;#225;l&lt;/p&gt;
</description></item></channel></rss>