O'Reilly logo
  • Chaitan Shet thinks this is interesting:

I was working with an organization in the Minneapolis area to gather metrics around cost. When I asked about Development Team costs, the stakeholders in the room responded that they had no access to salary information. Rather than remove or delay that metric, we decided instead to just search the web for average IT salaries in the greater Twin Cities area. We multiplied that number by the number of team members, which led to an estimated cost-per-Sprint metric. The important point here is that we want people thinking about costs, even if the number is not 100 percent accurate. We also want to just get started (often the hardest part) so that we have some sort of a baseline. If anyone who has the real information sees our metric a...