3 ms·

I've seen several comments about alternatives, and many more replies that say they suck worse than Jira.

• bamboozled 4y ago
  1. Have a competent trustworthy project manager work with product to come up with a roadmap, you then document the roadmap in a simple easy to read document which is hierarchical, and contains a list of initiatives to fit the roadmap. Under each initiative you can set a status and a target date and importantly, a team or individuals name who is in-charge of the roadmap. Project managers keep this document up to date. 2. Next, don't deploy JIRA here, just make sure everyone, and I mean everyone understands the roadmap and how they fit into it. 3. Work with those in-charge (who actually do the work) can choose their issue tracker of choice, or whatever method they like and the product management team ensures and trusts those they work with will have made the correct decision here. 4. Allow the dev teams to happily work in something simple like GH issues and be productive. When the product team wants updates, humans get together and talk about each initiative and how it's going. Simple. You might ask about tracking cOmPlEx iNtErDePeNdEnCiEs!!! that killer feature JIRA is about solving...I think that can be solved easily by ensuring managers have situational awareness (they should anyway) and everyone having the same issue tracker. For example GH issues so issues can be easily referenced.