3 ms·
> This is due to poor management. Strong management makes employees feel secure and not-surveillanced. Maybe that’s true, but having trustworthy async workload
by helen___keller 3y ago
> This is due to poor management. Strong management makes employees feel secure and not-surveillanced.
Maybe that’s true, but having trustworthy async workloads is dependent on having really good planning methodology (eg sizing tickets fairly accurately with 2 week sprint planning)
In my experience this is very difficult. The moment you start working on a more novel feature/project, ticket sizing gets wacky. When ticket sizing is wacky, you get the dreaded gray area: we planned this thing to take 3 days. It took me 1 day because the team didn’t understand how small the ticket was during ticket grooming. Do I take days off or create new work for myself? Am I responsible for post hoc fixing planning failures? If so, am I not just emulating the “spend 40 hours working” mindset via points? If not, am I not taking advantage of the teams planning mistake?
- bluefishinit 3y agoTracking ticket churn is not good management. Are your employees coming up with novel and effective solutions? Are they successfully implementing them? Can you hire and retain amazing people? Those are the only metrics that matter. If you hire high performers, your job is to keep them happy and clear stuff out of their way, not track them to the nth degree and force them into a bureaucratic project management labyrinth.