<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Craftmanship on Lucas Pardue - Bits &amp;&amp; Pieces</title>
    <link>https://lucaspardue.com/tags/craftmanship/</link>
    <description>Recent content in Craftmanship on Lucas Pardue - Bits &amp;&amp; Pieces</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 May 2014 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lucaspardue.com/tags/craftmanship/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Software Metrics and Craftsmanship</title>
      <link>https://lucaspardue.com/2014/05/26/software-metrics-and-craftsmanship/</link>
      <pubDate>Mon, 26 May 2014 00:00:00 +0000</pubDate>
      <guid>https://lucaspardue.com/2014/05/26/software-metrics-and-craftsmanship/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://lucaspardue.com/2014/05/26/software-metrics-and-craftsmanship/images/bottle-92418_640-300x199-300x199.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Software Development Metrics are a notoriously difficult area, there exists a&#xA;large allure of quantitative measurements that can be condensed into a top-level&#xA;dashboard showing progress, plan alignment, effort , costs and so on. However,&#xA;the unfortunate reality is that the collection and analysis of Software&#xA;Development Metrics is difficult for a number of factors such as complexity,&#xA;variance, meaning and gaming of the system. Often it is a difficult case of&#xA;understanding if we are more interested in the performance of the project&#xA;(Health) or the performance of the developer (Efficacy).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
