3 ms·
The problem, so to speak, is that companies are getting extremely data driven, and constantly need some form of metrics to evaluate their employees. This again
by TrackerFF 7y ago
The problem, so to speak, is that companies are getting extremely data driven, and constantly need some form of metrics to evaluate their employees.
This again can turn into a culture where doing what's expected is devalued to lowest score - because you have that system where there has to be bottom and top performers.
And you sadly end up with a situation where workers are (almost) embellishing their projects to get more visibility.
- ckosidows 7y agoMy company insists each ticket in Jira have a time logged on it now. This is on top of story points. Everyone I know has pushed back on it, but I hope this isn't becoming a standard elsewhere.
- bravoetch 7y agoProduct / project / scrum guy here. Logging time won't make sense unless each ticket is one person working on it at a time. The moment it becomes teamwork (like asking someone else for their thoughts on an idea) the value of time is meaningless. People are also useless at estimating time in advance, but pretty great with throwing a story-point number on a given story with the right guidance. Please feel free to schedule me in with your uneducated upper management. They're about to lose value.
- pjmlp 7y agoMany companies use Jira tickets to track employee time, instead of having a separate time tracking system. This creates a situation where everyone is searching for tickets to make up for their daily 8h.
- tambre 7y agoSame in the company I work at, but only for IT employees. It's fine as long you have over 80% of the monthly hours in you contract tracked. Definitely not used for micromanagement. I myself find it useful for seeing inefficiencies in what I do and ensuring I actually go home. It's handy for charging clients for development work specific to them.