5 ms·
I expected to read this as a "Ah yes, another JIRA bashing article." I've tended to view JIRA as "the worst of all project tracking tools, except for all the ot
by hn_throwaway_99 8y ago
I expected to read this as a "Ah yes, another JIRA bashing article." I've tended to view JIRA as "the worst of all project tracking tools, except for all the other ones" so I like to rise to its defense when I see folks complaining about it without taking into consideration the needs of other stakeholders.
That said, I've found myself agreeing with pretty much everything in this article. While I believe that JIRA (if properly configured) can serve as a good issue tracking system, attempts to do top-down, high level planning on it have always left me with nothing but frustration. My advice would be to completely ignore any of these features (e.g. all the "portfolio" add-ons), do high-level planning down to the epic-level in something else like Excel, and then map that to tickets in JIRA. The "Nirvana" of having complete visibility from very high, enterprise executive level planning down to the "what am I as an individual developer working on today" level in one tool is a false idol and just not possible.
- sb8244 8y agoAsking seriously: is it that it's not possible with today's tools, or philosophically not possible?
- throwaway9471 8y agoMy manager had a rule, that each member of the team was only allowed to have one unresolved ticket at the end of day. We had a weekly meeting where we would be badgered about every >1 unresolved ticket and had to come up with an action plan to make sure it never happened again. So coincidentally, we would "forget" to create a ticket for every issue, that would take more than a day, until it was one day from completion.
- praptak 8y agoI do sometimes follow this rule. Caveat: it requires unassigninig tickets that I'm not actually working on. It makes some people cringe in horror but once you start doing that it does wonders.
- Wowfunhappy 8y agoIs the idea behind this "I can only focus on one thing at once, so unassigning myself allows someone else to take up the task in the intirim", or something else?
- praptak 8y agoMostly this. Obviously, this assumes shared understanding of assignments as "things I'm working on" rather than "queue of things and also commitment do to everything". Combining the original "one open ticket" rule with the second approach is rather bad. That's why I hope it was used in the context of the first approach.
- achamayou 8y agoWhat gets measured gets done. If closing lots of tickets is seen as productive, you not only get lots of very granular tickets, but all sorts of grouping tickets and epics as well!
- jimjimjim 8y agoThis explains agile vs reality beautifully.
- mongol 8y agoBut all things considered, was the situation improved by that rule? I understand that it could be worked around ("cheated") but did it bring benefits as well?
- throwaway9471 8y agoIf someone has a reason for this rule, feel free to chime in. I believe it was an implicit way to tell us to do overtime off the books. Most of the issues, that took more than one day, couldn't realistically be completed in one day. Waiting on other parties, too many issues at once, low priority, etc. Occasionally, a ticket about something non-urgent, with no follow up from the business users, would get dredged up from the past to finally get worked on again. But I would attribute that to generally cleaning up unresolved ticket, rather than a benefit of the rule.
- lotyrin 8y agoThe theory would be that you can't have any more than one "thing I have started doing, and will resume doing first thing in the morning" which should be the meaning conveyed by "in progress" and everything else should be yet-untouched "backlog" or in a priority queue "prioritized" and therefore out-of-mind, or explicitly marked "blocked" with a comment about who or what is blocking it -- so that there's no question about why things aren't getting done or who is working on what (if everything on the board is sitting as "in progress") so people aren't over loaded, haven't bitten off more than they can chew, or have a bunch of things blocked but haven't raised their hand and spoken up about any of them (the typical dysfunctions).
- userbinator 8y agoThis is another excellent example of how making rules only tends to encourage working around them. Things get done when they get done, and no amount of managerial bureaucracy will make things go faster.
- kokokokoko 8y agoI'll try to explain the perspective some people have, including myself, about tools like Jira. I do not believe that what Jira attempts to accomplish is possible. Organizations tend to utilize Jira to automate project management. I see that as a mistake. I want managers and project owners to be forced to keep the entire project in their head as much as is humanly possible. Software development is a messy process with a lot of moving parts and cliffs someone needs to be looking for to avoid going over. With Jira I see people attempt to essentially automate keeping track of the project and they stop having a high level and deep understanding of the project. I think Jira helps make certain role's jobs easier, as opposed to making them perform better. In shops where Jira is heavily utilized, most developers and managers tend to get in their own little worlds at the expense of the project as a whole. Which again is because not having to worry about the entire project is more comfortable for everyone at the expense of the overall success of the project. I find that smaller more specific tools solve enough of the problem of project organization and tracking without the side effect I described above. I know this is a bit of a hot topic and I understand and appreciate that many people do not share my opinion.
- bunderbunder 8y agoI'd go so far as to say that, when I'm wearing my project manager hat, our tool (which isn't Jira, but is similar) actively wants to make things worse. When I'm wearing my product manager hat, it's simply a disaster. Sticking everything in a ticketing system makes keeping a project organized more difficult for the same reason that owning lots of stuff makes keeping your house organized more difficult. There's only so many random odds and ends a person can be expected to keep neatly arranged. Especially if keeping them arranged is tangential to their actual job. I got a lot more effective at my PM responsibilities, with a lot less time spent doing it, after I laid some ground rules limiting the use of ticketing system on my project. One of the main rules was, if nobody needs to be actively thinking about it right now, it doesn't get a ticket.
- ozim 8y agoI have seen attempt to make project roadmap for next 6 months in JIRA, that was terrible. It is confusing for developers, it is confusing for business people, you cannot show it to the customer because they don't care about your tickets. It was too much of work to go through it so stuff that was not built because prio changed had to be closed and all clicking around taking too much time. I think you should have next 2 sprints of work max in there, probably better if you only make stories for next sprint.
- bloomca 8y agoIt depends on your problems. Small companies have different problems in mind than big ones, so it might work pretty well for some smaller companies. In big companies, as GP said, it is often a utopian idea of full transparency and automatic progress generation in one click. Reality is more complex, of course. JIRA is omnipresent, therefore critique should be taken with grain of salt – you can find complaints about too vague tickets/user stories and complaints about too detailed tickets (with implementation details).
- munchbunny 8y agoThe limitation isn't really our tools, to some large extent it's our brains and our ability to wrap our head around the whole pyramid. In a tiny startup that might be manageable, but even at 20-30 people you have to start abstracting. When you choose to use JIRA for something, you are giving up an organizational dynamic where you previously depended on judgement, and you are now handling it with process. Judgement is adaptable but very hard to scale, process is rigid but maybe too easy to scale by fiat (whether it's a good process is a different question). To be clear I don't mean that your PM's become mindless drones the moment you standardize on JIRA. I mean that where previously your 1-week projects and your 6-week projects would use custom planning processes, now with weekly sprints the 6-week project has to subdivide itself. There may be good reasons to subdivide longer projects, but I think this is an example of the class of problems that come from reality slipping through the cracks of processes. When you look to JIRA or any other tool for the answer, you have to make sure you are not implicitly giving up the role that judgement plays as the safety release valve for procedural red tape. In that sense it's not even the tools' fault, because you can't blame them for trying. It's that the organization has to see the tool as "just a tool".
- pzs 8y agoI think that in a large enterprise organization the scale of people who would have to interact with such a tool (from executives to developers) have reasonably different interests about what sort of information would be helpful for them and in what arrangement. As a thought experiment I can imagine one monolithic monster tool that could cater for all these needs. However, I think its complexity would render it utterly unusable. Much like there is no one person who can work comfortably at each and every level of the org. Alternatively, this hypothetical tool may be a chain of components/screens/etc. mirroring the various levels in the org. However, I think they would likely provide unusable outputs, because without the precise understanding of how these components build on each other people using the tool wouldn't be able to populate inputs correctly and data may be wrongly classified/consolidated or lost (filtered out) very easily. There is also infinite flexibility needed for such a tool because as middle management comes and goes they come up with various creative ideas about how to present progress and added value. This may lead to frequent changes in properties that can trickle down to the bottom without any well-defined meaning. To sum up, I think it would just not be practical.
- goalieca 8y agoIt boils down to micromanagement. Engineers shouldn’t be managed by small tickets. They should be given bigger scope of work and manage themselves.
- hn_throwaway_99 8y agoDepends on who else needs visibility. I definitely agree developers shouldn't be micromanaged, but IMO there is no such thing as an "80% done" ticket - it's either done or it's not. So things may need to be broken down a little more than a particular developer would want so that other team members (e.g. QA, design, management, etc.) can pick up their own tasks if they are dependent.
- Karrot_Kream 8y agoIsn't that the point of planning meetings and standups? To audit whether the tickets and the work actually solve the greater product need?
- hn_throwaway_99 8y agoAt the individual team level, yes, that is the point. However, at a higher level, my opinion is that JIRA sucks for this. For example, a company may have a high level initiative like "Move our infrastructure to the cloud." That initiative would then require projects from lots of different teams, and would require investment to make sure resource allocation is adequate. I've seen orgs try to handle all of this in JIRA, i.e. where the high-level reports given to senior execs who really just want to know "what percentage of our stuff has been migrated to the cloud" are generated from JIRA, and it always is a major pain in the ass that doesn't actually give a good view into what execs want to know in any case.
- Karrot_Kream 8y agoOh yeah, doing this at a higher level sounds awful
- kevinb7 8y ago> I've tended to view JIRA as "the worst of all project tracking tools, except for all the other ones" I've seen heard this opinion a number of times and I don't believe it's true. TargetProcess is a better project tracking tool. It has a deeper hierarchy for organizing work. It has the concept of teams built-in and allows you to view work across multiple teams and/or projects. It also provides a way to do roadmaps built-in. Everything is included and everything is designed to work well together. As for the specific criticism about not being able to get a high-level and low-level view in one tool, I think the reason why JIRA does poorly at the high-level view is that it has a very shallow hierarchy of work entities. It has epics => user stories => sub tasks. While projects can also be used to organize work, JIRA unfortunately binds the concept of sprints which is more of a team thing to projects. Thus it's difficult for one team to work on multiple projects or multiple teams to work on a single project. TargetProcess on the other hand has a separate entities for teams and sprints which allows projects to be used for organizing work. It also has an additional level in the work hierarchy providing the following levels: project => epic => feature => user story => task. This deep hierarchy allows you to group work into larger groups allowing you to see both the high-level and the low-level. https://www.targetprocess.com https://www.targetprocess.com
- jib 8y agoJIRA does not have those problems. Portfolio allows for multiple layers on top of epics. Boards can be set up to pull from multiple projects, and boards are what are tied to sprints, projects are not tied to sprints (mostly, there’s some oddities). Portfolio is implemented somewhat badly (Why the hell can’t I do skip level relationships?) but it certainly has the features you say you’re lacking.
- perlgeek 8y ago> JIRA unfortunately binds the concept of sprints which is more of a team thing to projects I believe this has been fixed for some time. https://community.atlassian.com/t5/Jira-questions/How-do-I-create-a-sprint-with-tasks-from-multiple-projects/qaq-p/318386 https://community.atlassian.com/t5/Jira-questions/How-do-I-c... https://community.atlassian.com/t5/Jira-questions/combining-multiple-projects-into-1-sprint/qaq-p/418806 https://community.atlassian.com/t5/Jira-questions/combining-... I agree about the too small number of hierarchical nesting though.
- hliyan 8y agoThis is exactly where I'm at. JIRA is a great tracking tool, but a horrible planning tool. I've moved most of the planning to Excel...