You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are a growing startup with a dev team of about 40 people.
We work in an agile environment and we have 4 teams (each team has their own PM, frontend, backend, UI/UX).
Right now we work with JIRA to manage our bugs (also test cases in the past - we don't write new ones now).
And the teams are using Trello for their sprint.
They absolutely LOVE Trello, which I can understand, as it's a very agile and easy to use tool compared to JIRA.
BUT, as we grow, we must move to a centralized tool with greater capabilities.
For example, right now, the Head of Engineering can't see in real time and historically how the teams are doing. So we can't measure and learn. that's bad.
The PM's really "hate" JIRA, but my feeling is that they "hate" it because they just really love their process and they feel that JIRA is more corporate and "heavy" tool.
Can you help me from your own experience to bring good arguments on why we should move to a centralized tool (first) and that the tool should be JIRA (second), as we already know it and using it for bugs tracking.