3 ms·
The thing is, they don't have a metric for me to hit. For example, my throughput is the same as the other midlevel dev on the team who is doing well. If it was
by giantg2 2y ago
The thing is, they don't have a metric for me to hit. For example, my throughput is the same as the other midlevel dev on the team who is doing well. If it was the metric, I'd be hitting it already (at least according to the only indicator I have for what that metric might be - the other dev doing well).
Some sprints I'll close multiple stories because they don't have impediments. Then I hit sprints where my stories all carry over (yes, I'll have multiple open to fill the downtime, otherwise I'll get even more scrutiny). So my average is good, but my consistency isn't, and is basically beyond my control.
- sircastor 2y ago> The thing is, they don't have a metric for me to hit. Get this is writing. An email outlining specifically where you’re coming up short and the metric that works address it. Print that out in duplicate and keep a copy in a safe spot. If they can’t provide a metric you lay that at their feet and point out that you’re averaging out the same as others. If they do provide hard metrics, meet those (or evaluate if they’re trying to give you an impossible task) Don’t accept this as defeat. I was once notified that if I didn’t shape up I’d be put on a pip. I fixed it, and confirmed with my manager and project lead that everyone was happy. I was with that company for another couple of years. That said, assume that they are gunning for you and collect as much evidence as possible that counters what they’re saying. If they want to fire you, that’s their choice, but if you can refute what they’re saying and what they’ve asked you to do with evidence, you’re building a strong case for whatever your severance is going to be. Start looking for a job now. Work both ends of the situation. Good luck. I hope everything works out in spades for you.