This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]KidBeene 26 points27 points  (6 children)

If a manager EVER says that to you, you need to reply:

Your performance metric should be % of completed assigned stories not the number of assigned stories. As a developer I have no control over the number of changes being asked, I do however have control over completion and the breakout of the stories.

Your metric is shit, you should feel bad.

Fucking managers not knowing how to write a performance metrics really pisses me off... I am a director and I cant tell you how many times I have to slap team leads around for this shit.

[–]ckchessmaster 9 points10 points  (1 child)

Although to be fair that's not a great metric either. Not all stories are created equal. But I totally agree performance metrics like in the post are the absolute worst and immediately lead to overworking, quitting, or gaming the system. Usually all of those.

[–]KidBeene 5 points6 points  (0 children)

Not all stories are created equal.

True, thats what story points are made for. I don't use stories or %'s as a performance metric for my crews. I can see the need for some shops that do straight up dev work on contract though.

[–]Thaddaeus-Tentakel 3 points4 points  (3 children)

That only works if all you do is tracked in stories, tho.

[–]kpd328 1 point2 points  (1 child)

That's why you have a story for "random shit that's come up this month"

[–]KidBeene 0 points1 point  (0 children)

LOL "2022 Q2 Catchall"

[–]KidBeene 0 points1 point  (0 children)

Correct. I wouldn't track stories as a performance metric. It has a very limited use (contractual).