What is funny about this is that Atlasssian’s Jira product is designed for two week “sprints”, a term referring to the idea of running quickly at a rate above a sustainable pace with no intent to keep running after the end. But these sprints normally are done repeatedly with no actual stop or sight of a finish line. Employees just churn through tickets with no designed breathing room or planned downtime. Jira is prob…
There are reports produced that developers don't get to see that the manager does to compare developers this way.
Of course, this can be easilly gamed. The most cunning developers will go out of their way to get the tasks that are clearly defined in scope and that they are familiar with, while others always end up getting the short end of the stick.
Guess who is going to look better under that report. Developers are overloaded, and will actually avoid to raise new issues or suggest improvements and new tasks, with fear that they will get more work on top of the workload that they can't already handle.
JIRA is really used by middle management to treat developers as essentially replaceable assembly line workers in a factory context.