My process is similar. I use Trello with four lists: Backlog (further out feature ideas, ambitious or less important refactors, edge case bugs), To Do (basicall

My process is similar. I use Trello with four lists: Backlog (further out feature ideas, ambitious or less important refactors, edge case bugs), To Do (basically an extension of Backlog for things I plan to work on imminently), In Progress and Done. I also have labels: Feature, Bug, Refactor (user-impacting things like improving performance), Developer (non-user-impacting things like importing infrastructure into Terraform) and Marketing. One thing that has helped me immensely is using checklists on Trello cards. Unless a task is very simple, I generally make two checklists: one for implementation and one for QA. The act of making an exhaustive QA checklist in particular has helped me figure out edge cases that affect feature development, and going through each and every scenario outlined before releasing has caught a ton of bugs. As a bonus, I get a progress meter on each task. It's enough structure that I have a good handle on everything, but loose enough that I don't spend much time appeasing my product management process. I'm only coordinating with myself here, so I think adding more tools or processes would just slow me down.