Why your team hates Jira — and how to fix that

Team Troopr
Troopr
Published in
2 min readFeb 17, 2020

Agile process optimizations that are a win win win!

Photo by Jeff Sheldon on Unsplash

Jira is used by estimated 65% of the agile teams around the world and is the undisputed leader in agile project management tools by far.

For all its shortcomings, Jira is still the most powerful tool out there and loved by vast majority of scrum masters using them (85% of project managers using Jira recommend it for agile teams). So why do a people who execute on planned work still hate to update Jira.

Jira is seen as clunky, slow and unintuitive to use*. As a team member, if it is not in my job description to manage work in Jira, I do not want to spend time figuring out how to deal with Jira. Ideally tools like Jira should get out of the way, not get in the way of the real work.

While Jira product Ux is improving with every release, scrum masters can do more than wait for new product updates from Atlassian. By introducing process optimizations to minimize the friction in updating Jira, scrum masters can create a win win for team members and stakeholders alike.

While Jira is the defacto agile project management tool, Slack is the leader in chat platform for agile teams. Jira Slack bots are a popular way to collect Jira updates directly where the team is discussing them. Slack Jira integration is available from Atlasssian themselves and from vendors including Troopr.

Troopr, a digital assistant for agile teams, provides a complete agile process automation solution for teams using Slack and Jira. See here for more.

Why integrate Jira and Slack?

  • Slack is where your team is collaborating already
  • Improved odds of keeping Jira current
  • Automated transactional interactions in Slack to save time
  • Automated nudging for updates
  • Switch from Email to Slack for actionable notifications
  • Shared insights with Jira Reports in Slack
  • Automated Jira activity summaries in Standup Reports in Slack

Automations that are good for your business

  • Proven to improve team productivity and save time
  • Maximizes ROI on Jira investment
  • Upgrades employee workplace experience

Read more about these automations here.

Why this is a win, win, win

(for team members, scrum masters and stakeholders)

  1. No more “dealing with Jira” for team members
  2. Less “asking around for updates” for Scrum masters
  3. More accurate Reporting for Stakeholders

Make Jira work better for everyone in your team. Try Troopr’s Jira Slack Integration

References:

Annual State of Agile Report

15 reasons why Jira and Confluence suck

Why People say they hate using Jira

--

--