Once again, best of luck!
I don't know how far this will go or if it'll be successful, But I gotta give it a go.
To be fair, they do not care about any specific individual developer. And I don't bother tracking individual dev performance. I track the overall delivery cadence.
Where I do care about individual developers is knowing how much they stay on-task. My teams vary from someone who will always do exactly what is outlined in the ticket, to people who second-guess and redesign the work (sometimes for the better, sometimes not), to people who go off the rails and design grand future visions that we then need to scale back to reality.
All of those people have value, but I need to manage their working style to the short-term business needs when planning upcoming work - sometimes I can let them fly free, sometimes I just need someone to put a freaking button on the screen and ship it.
So yes, it matters... micro-managing is pointless, but high level tracking helps set the correct pace of delivery.
It is more a power play by the "Management" rather than satisfying any actual need. While some amount of management and issue/time tracking is necessary the intense focus on the same by Agile/Scrum is useless and counter-productive.
If you're interested, sing up to be notified when I have the beta version ready. Hopefully in a month or two. If not, tell your friends.
Thank you Terry
I just wanted to see if there was interest. Looks like there is. That's awesome.
I'll spend some time this week adding more details to the page.
I think sprints enforced by the interface is critical to keep management on track. The companies I worked at which used Asana, Trello, or free-form task lists were a mess. It was maddening not having a single schedule.
