what tracker are you using now? Jira is better than Trello for large projects, and better than Hansoft because it has a clearer workflow.
Trello is much better for small projects with only a few developers though.
but that’s just, like, my opinion. I’ve worked with Jira for almost 10 years so I’m biased.
if there is agile brainrot in your organization, expect it to continue, I’d say. if you already have people hassling you about story points and epics now, it’ll be about the same. if not - buckle up, they might get encouraged.
producers and other project people love Jira but so does QA, and as a dev I want QA to thrive so I’ll take the good with the bad.
Maybe try to get them to use the simple Kanban workflow to get started, and test out adding features slowly (but never let them by rallying the workers to your cause)
what tracker are you using now? Jira is better than Trello for large projects, and better than Hansoft because it has a clearer workflow.
Trello is much better for small projects with only a few developers though.
but that’s just, like, my opinion. I’ve worked with Jira for almost 10 years so I’m biased.
if there is agile brainrot in your organization, expect it to continue, I’d say. if you already have people hassling you about story points and epics now, it’ll be about the same. if not - buckle up, they might get encouraged.
producers and other project people love Jira but so does QA, and as a dev I want QA to thrive so I’ll take the good with the bad.
This is what I’m worried about. And we are our own QA so that advantage isn’t super helpful unfortunately.
Maybe try to get them to use the simple Kanban workflow to get started, and test out adding features slowly (but never let them by rallying the workers to your cause)