TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The use of JIRA is (often) a symptom of a Management problem

43 点作者 bwghughes超过 9 年前

9 条评论

joshstrange超过 9 年前
Very misleading title IMHO... A couple excerpts:<p>&gt; I have no beef with JIRA per se, but its the one we come across the most. &gt; Here’s what a colleague said, just this morning about JIRA: &gt;&gt; We must ensure JIRA usage is identical across teams, in order to ensure velocity parity<p>&gt; 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.<p>Uh... then don&#x27;t work for company with shitty management... This has absolutely nothing to do with JIRA. You could find and replace &#x27;s&#x2F;JIRA&#x2F;Rally&#x2F;&#x27; 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&#x2F;hurt that really...
评论 #10582354 未加载
评论 #10581122 未加载
UK-AL超过 9 年前
Click Baity title. Has nothing to do with JIRA but trying to compare velocity between teams.
kylecordes超过 9 年前
I followed a few links, and didn&#x27;t see much background information about Ben&#x27;s experience with companies using JIRA at scale; from the tone of the posted sounds like he is seen some bad management and action.<p>But here&#x27;s another point of view; at work we (among other things) train and consult companies on effective use of JIRA. As best we can tell, our students and clients are well-intentioned, trying to use JIRA for good, not for evil. They often want something similar to what Ben wrote about, to get numerous projects and teams across a large organization using the same tracking tool (JIRA) in approximately the same way, with local variations as needed but avoiding pointless variations.<p>I&#x27;ve actually not heard of any of them trying to &quot;ensure velocity parity&quot;, but rather the typical goal is to be able to roll up and understand project status and progress across a large and sprawling organization working on goals that far exceed what an individual team could do. This seems like a worthy and important goal.
评论 #10582750 未加载
nowprovision超过 9 年前
Sounds like a shitty company, you&#x27;re probably missing much bigger symptoms.. Get a new job<p>JIRA is [s]fine though[&#x2F;s] ok, I&#x27;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.<p>Clojure use it to track issues too, and very few moans (surprising given the amount of hammock time devoted to simplicity)..<p>Disclaimer: At one point prior to using JIRA I did retweet &#x27;&quot;Im so happy we use JIRA&quot; - no programmer ever&#x27; or something like that, cargo-culting jira hate?
karlkatzke超过 9 年前
The author has an incorrect definition of Taylorist management.<p>&gt; Now obviously this is a blatant transgression — absolute, unequivocal application of Taylorist management in the context of a Product Development mindset<p>From the Wikipedia article that <i></i>HE LINKS<i></i>, this caveat is given as to why Taylorist principles still sometimes apply:<p>&gt; 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.<p>And that&#x27;s what JIRA is used for in most companies.
评论 #10583479 未加载
code4tee超过 9 年前
Crappy teams and bad management creates management problems, not tools.<p>JIRA is fine. So far as &quot;enterprise&quot; tools go I&#x27;d actually say it&#x27;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&#x27;t make up for crappy teams... and honestly good teams will find their way to work with&#x2F;around bad tools. However if you have crapy teams and crapy management then you&#x27;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.
alistairSH超过 9 年前
This blog elicited a chuckle. My employer recently mandated JIRA for all teams, even those teams which have been using other agile tools for years. No good explanation was given.
评论 #10581397 未加载
debacle超过 9 年前
Centrally mandating the use of a tool is not a management problem.<p>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&#x27;s time.<p>&gt; We must ensure JIRA usage is identical across teams, in order to ensure velocity parity<p>In real talk:<p>&gt; We want to standardize our time accounting across teams to ensure everyone is moving as fast as possible.<p>How diabolical.<p>The bemoaning of having to do basic project communication is a symptom of a novice professional.
mtVessel超过 9 年前
cum: <a href="http:&#x2F;&#x2F;grammarist.com&#x2F;usage&#x2F;cum&#x2F;" rel="nofollow">http:&#x2F;&#x2F;grammarist.com&#x2F;usage&#x2F;cum&#x2F;</a>