I worked in a dev team for the last 8+ years and used Jira in most of it. I mostly hated it, literally!
- I have no problem with the Agile Development cycle. They way Jira handles all those epics, stories, etc. adds too much overhead. I feel like Github Project boards, or even Trello does a better job.
- Starting to work on a task and moving it to the finish line can take as much as doing the task itself (in case of a small bug). I admit this is also related to how Jira was set up, but I haven't seen a smooth workflow yet.
- I had to create an "Issue Reporting Tool" that works with the Jira API. As luck would have it, Atlassian was in the middle of updating their API authentication. API documentation and the actual API were not on the same page. Jira's support failed to recognize the problem, and I chased my tail for two weeks. Finally, I proved the inconsistency with some "undeniable" proofs, and finally, support pulled their head from the sand and admitted the issue. I had better support experiences with free Softwares (i.e., ArangoDB).
I know Jira is so popular among programmers and some people might even love it, but I cannot shake the feeling of "Project management should be this cumbersome!" Am I missing something?
The biggest complaint I’ve heard about Jira from team members is that it’s a ‘heavy’ solution. Yet for large teams or teams that want a lot of structure, it does the job better than most other solutions. If the team /company is smaller, a lot of those feature become overhead. Also if your team doesn’t need all the structure, then Trello might be better. If you want something in the middle, Clubhouse is a good compromise between the two. Just like there isn’t one type of car for everyone, there isn’t one agile project management tools that perfect for all teams.
Jira is very flexible and often tends to be abused by setting up a complex processes, but I dont belive Jira force you to add structure and overhead, but often ends up as that. I dont think is a problem of the tool itself but how sometimes its used.
I believe things can be effiecient end effective, even with simple solutions such as postit on a wall, and also like the concept of Card-Conversation-Confirmation: https://www.agilealliance.org/glossary/three-cs/
Atlassian has sadly taken the same approach to their products that SFDC did, which is to force you to their channel partners for the purposes of customization, then upselling. Their platform is far too complicated for the average person to administer, and their marketing is overbearing. Jira itself is a decent tool, and my team is stuck with it for now, but I would rethink that if I was starting from scratch. I give them credit for being very receptive to feedback and pushing updates very often.
Setting it up for a simple workflow is possible. Problem js that Jira wants to be able to do it all. So much flexibility comes at a price: complexity. Basically Jira is an excellent administration tool for ‘agile’ work but my issue with it that is does not support the team (you can fill your sprint with all your backlog stories and Jira won’t support you with the notion that sprint will probably not reach its goal.
We have 15k newsletter subscribers, and have around ~2k of them in a Slack group. We're starting to encounter issues in terms of community management - specifically, it's hard to pin content like c...
Google lets you subscribe to a calendar using a URL - although when using an Outlook 365 Calendar link, events are copied over once, and then the syncing stops. This seems to be a relatively new is...
Three major considerations I have been using to evaluate the plethora of options available: 1. Effortless/non-intrusive: It shouldn't feel like a video call 2. Price: As this app would be complime...
I never set up Jira myself; it was done by a 'Scrum Master' in companies I worked for. The overhead might be coming from their way of setting the Jira.
I asked for a simpler workflow to use within the internal project. (todo - in progress - done) and I was told, "Jira is not that simple"...
I never confronted the scrum masters but never really bought the excuse either.
Since I am giving a second thought about my experience with Jira, I started to think my dislike is mostly coming from the Scrum Masters' choices.
You can customize the workflow but you need to have admin privileges. You'll have to decide if its easier to use a simpler tool or get your scrum master to create a simpler workflow for your project
Actually, it was just another irony at the company I worked for. We are trusted with the "project", our code goes into production, and so many people use it (~5+ million users in my case). But we, programmers, had no access or saying how to run "project management".