gitlab.
Maybe someone might be able to tell me where my thoughts fall into. The methods I use involve utilising all of gitlab.
So, I take the roadmap per quarter, as created by the founding/senior management team. Then I split those high levels ideas down into monthly milestones. Each milestone has it's own issues, which are assigned to teams or individuals, with all the relevant information and people involved. So I guess it's waterfall?
But I also take into account customer requirements & deployments so if anything does come in then it can be quantified and prioritised in order to ensure the dev team aren't doing something that's not needed or not of critical priority.
Gitlab has kind of like a trello board for issues within each project/product so it's easy to track and maintain. I also use the "estimation" stuff too, which provides feedback on accuracy of predicting timeframes for issues allowing me to improve the predictions and surrounding processes.
My next steps are to allow users of my product to automatically submit issues to the project via email. I.e. they email support@me.com then I get an email to my inbox and it also automatically creates an "Unclassified" or "pending" issues in gitlab with a custom template and then I'd review the issue to determine if it's a new feature, enhancement or bug along with a priority. Once the issue is complete/fixed then an automated email would be sent back to the user/email who submitted the issue and tell them something like "the issue has been fixed/you will see this new feature in release X.X.X at date XX/XX/XXXX."