The consultancy giant has devised a methodology they claim can measure software developer productivity. But that measurement comes at a high price – and we offer a more sensible approach. Part 2.
I started reading this article with the mindset that it provides an alterantive to McKinsey's approach of measuring developer productivity. I am diasspointed. It does elaborate on obvious things but it doesn't have an answer. I would rephrase the question that still stands.
Even if my team is doing good enough, how do I measure individual's productivity to reward them or give proper feedback to executives in case of downsizing?
I started reading this article with the mindset that it provides an alterantive to McKinsey's approach of measuring developer productivity. I am diasspointed. It does elaborate on obvious things but it doesn't have an answer. I would rephrase the question that still stands.
Even if my team is doing good enough, how do I measure individual's productivity to reward them or give proper feedback to executives in case of downsizing?