Learn More
Resend Email
12
cho-uc
2y

How can I make my manager understand that performance should not be measured by how many tickets we have resolved?

If the ticket is an easy one then sure 1-2 days is enough, but for some complicated shit or dealing with models that I have never touched before, I am gonna need several days just to understand the requirement.

For some fucked up reason, our story point is in hours, instead of days. So when we say 24 hours, then it's only 3 days.

Another fucked up reason is that my colleagues doesn't seem to mind. I am the most vocal one objecting when got assigned too many tickets. They just joke around and seem to accept it.

FYI, I am just 6 months in and bouncing between 3 projects.
Am I just too lazy or slow?
In my previous company, the devs seemed to be pretty chill, and the project manager only complained when an issue has been dragging on for weeks.

rant

jira
Favorite
Ranter
Comments
  • 4
    2y
    Tasks shouldnt be estimated in hours, that just puts too much pressure one devs. I think any place that does it is a sweatshop. I mean some days devs will have meetings and etc. so even those "3 days" can quickly become 4 or 5...
  • 6
    2y
    Estimation game:
    you look at a task, and think... 1 day.
    You say, this will take me 3 days.
    your boss hear 3 days, and update to 6 days.
    Why? because meetings. And overhead. And unknown tech debt. And you got sick. And food. Traffic. Whatever.

    Stop obessing, start padding.
  • 7
    2y
    Cut your tickets to miniscule ones so you get more tickets, and thus more work, done.
  • 1
    2y
    Story points aren't supposed to be a time unit.
  • 1
    2y
    Do as @electrineer said, make a script that opens 1000s of tickets and assign them to you. Then solve them all by fixing a typo in a comment or something.
    Nothing devalues a stupid metric like hyperinflation.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment