News for hackers. Stuff that matters.

A comment on True cost of recruiting a developer [infographic]. Parent comment

Re:True cost of recruiting a developer [infographic] by struppi on Wednesday December 21, 2016 @01:22AM (#13227180)
I know that this every productivity measurement is very fuzzy and can be cheated (#), but here's how we did it:

We were simply looking at the number of features delivered to the customer in a certain amount of time, number of defects found in production and number of critical defects found immediately after roll-out (a.k.a. hot-fixes). We adjusted for holidays, vacations and sick leaves.

Those numbers were relatively stable until we changed the team, then dropped, and it took quite a while to reliably get to higher levels than before.

(#) I don't think the team cheated, because if they had, they could have easily cheated the numbers in a way that they'd steadily rise.

[ Parent | on HN ]
Re:True cost of recruiting a developer [infographic] by flukus on Wednesday December 21, 2016 @01:52AM (#13227300)
> Those numbers were relatively stable until we changed the team, then dropped, and it took quite a while to reliably get to higher levels than before.

That could be a reflection on a number of things, most notably the code quality. If your new hires are taking a while to get up to speed (you didn't specify how long) then that's also an indication of either quality or doing something quite different.

[ Parent | on HN ]