4 ms·
Agree with not going overboard with stats and Jira. However being good with these tools to help measure velocity and improve the quality of estimates reduces t
by cube00 10y ago
Agree with not going overboard with stats and Jira. However being good with these tools to help measure velocity and improve the quality of estimates reduces the pressure on the team when clients plant the seeds of doubt that you've over estimated.
- marktangotango 10y agoI agree it's possible to go overboard, but I find that a lot of developers don't appreciate how useful it is to have documentation of what the team is doing and visibility (ie numbers) into how time is being spent. A lot of developers hate tracking task in jira or any task tracker, but whenever deadlines start being missed due to roadblocks thrown up by other teams, or ineffective project management, having that all documented can really help resolve toxic situations.
- atmosx 10y ago<rant> I don't know, Jira feels like a conspiracy theory in action: Atlassian somehow tricked management into adopting JIRA. Then the management had to pay insane prices for external plugins in order to allow programmers to do trivial things like displaying in a visually appealing way hours spent over a week. It's really an awesome business model. Worked great for Microsoft. </rant>
- ci5er 10y agoThen one of the requirements on the project manager would be to communicate what his own constraints and objectives are to the team, right? One could imagine a PM saying to the team: "I go to meetings so you don't have to. But one of the tools I use to keep the finance people happy enough to keep this project fully staffed is those stupid metrics. Help me help you by filling them in."