3 ms·
> Your primary work tracking tool is not good enough to allow people to see who is working on what, and what the status of that work is? You can't get an overvi
by javagram 7y ago
> Your primary work tracking tool is not good enough to allow people to see who is working on what, and what the status of that work is? You can't get an overview of what is being worked on? You can't check on a specific issue to see how far along it is?
In my experience most people don’t regularly post summaries of their progress on their ticket. Even getting certain people to update their ticket descriptions at all (to add test instructions or to reflect that they decided to do something other than originally described) usually requires reminders.
This may depend on team culture but in my experience a lot of people just aren’t written communicators.
- lazyasciiart 7y agoOr communicators at all. It's like pulling teeth to get some of them to expand on "oh, it's blocked, I have to talk to Bob"
- whateveracct 7y agoWe're all professionals - we can learn new skills when they're high-value (like updating tickets with written communication) I don't like the sentiment that developers doing things out of their comfort zone (like using JIRA) is unreasonable. Just get over it and be a professional. That said, it's on others to motivate the use of such tools. It's easier to get buy-in when everyone understands the value.