The use of JIRA is (often) a symptom of a Management problem
1–10 of 25 posts
Re: The use of JIRA is (often) a symptom of a Management problem
#2Centrally mandating the use of a tool is not a management problem.
When you need to try and account for where your time is going, there are two ways - have everyone use a slightly crappy tool that they loathe (mostly for its purpose), or have some sort of process in place that is less efficient with everyone's time.
> We must ensure JIRA usage is identical across teams, in order to ensure velocity parity
In real talk:
> We want to standardize our time accounting across teams to ensure everyone is moving as fast as possible.
How diabolical.
The bemoaning of having to do basic project communication is a symptom of a novice professional.
Re: The use of JIRA is (often) a symptom of a Management problem
#3Very misleading title IMHO... A couple excerpts:
> I have no beef with JIRA per se, but its the one we come across the most. > Here’s what a colleague said, just this morning about JIRA: >> We must ensure JIRA usage is identical across teams, in order to ensure velocity parity
> So, clearly this is no fault of JIRA — I (as I’m sure you) have seen it used many a time successfully, but all to often, it is used (and abused) as a top down management tool, mandated from the centre.
Uh... then don't work for company with shitty management... This has absolutely nothing to do with JIRA. You could find and replace 's/JIRA/Rally/' and while the article would still be wrong it would make as much sense. There is nothing inherently wrong with JIRA itself. If you have shit management then you have shit management and no tool is going to help/hurt that really...
Re: The use of JIRA is (often) a symptom of a Management problem
#4Click Baity title. Has nothing to do with JIRA but trying to compare velocity between teams.
Re: The use of JIRA is (often) a symptom of a Management problem
#5Very misleading title IMHO... A couple excerpts: > I have no beef with JIRA per se, but its the one we come across the most. > Here’s what a colleague said, just this morning about JIRA: >> We must ensure JIRA usage is identical across teams, in order to ensure velocity parity > So, clearly this is no fault of JIRA — I (as I’m sure you) have seen it used many a time successfully, but all to often, it is used (and abu…
Right and as it says in the title, use of JIRA is often a symptom that there is a problem with management. Nowhere is it stated that JIRA itself is the problem.
Re: The use of JIRA is (often) a symptom of a Management problem
#6Sounds like a shitty company, you're probably missing much bigger symptoms.. Get a new job
JIRA is [s]fine though[/s] ok, I've used when at a HN hip company, and it worked really well, granted it could have been a little simpler, but still much better than any homegrown alternative, and it was on-premise too.
Clojure use it to track issues too, and very few moans (surprising given the amount of hammock time devoted to simplicity)..
Disclaimer: At one point prior to using JIRA I did retweet '"Im so happy we use JIRA" - no programmer ever' or something like that, cargo-culting jira hate?
Re: The use of JIRA is (often) a symptom of a Management problem
#7The author has an incorrect definition of Taylorist management.
> Now obviously this is a blatant transgression — absolute, unequivocal application of Taylorist management in the context of a Product Development mindset
From the Wikipedia article that HE LINKS, this caveat is given as to why Taylorist principles still sometimes apply:
> Although scientific management as a distinct theory or school of thought was obsolete by the 1930s, most of its themes are still important parts of industrial engineering and management today. These include analysis; synthesis; logic; rationality; empiricism; work ethic; efficiency and elimination of waste; standardization of best practices.
And that's what JIRA is used for in most companies.
Re: The use of JIRA is (often) a symptom of a Management problem
#8Very misleading title IMHO... A couple excerpts: > I have no beef with JIRA per se, but its the one we come across the most. > Here’s what a colleague said, just this morning about JIRA: >> We must ensure JIRA usage is identical across teams, in order to ensure velocity parity > So, clearly this is no fault of JIRA — I (as I’m sure you) have seen it used many a time successfully, but all to often, it is used (and abu…
Right and as it says in the title, use of JIRA is often a symptom that there is a problem with management. Nowhere is it stated that JIRA itself is the problem.
So the title should've been 'the use of an issue tracker is a symptom of a management problem'. But that title is absurd, hence the click bait title.
Re: The use of JIRA is (often) a symptom of a Management problem
#9[deleted]
Re: The use of JIRA is (often) a symptom of a Management problem
#10Crappy teams and bad management creates management problems, not tools.
JIRA is fine. So far as "enterprise" tools go I'd actually say it's quite decent. Good teams need ways to collaborate and communicate on projects and JIRA has a lot of good features to do that as do other options out there. However, at the end of the day good tools don't make up for crappy teams... and honestly good teams will find their way to work with/around bad tools. However if you have crapy teams and crapy management then you're basically just screwed... but you know someone will decide to do another pointless re-org or something dumb to try and solve the problems.