When your application is scheduled to go to production, the development team may be asked what their regression testing strategy is. This is a perfectly reasonable question, but a lot of people have a hard time answering it. Don't overcomplicate it. Analyze your process, look at the other testing, and put it together.

While using index cards and a wall can function just fine as a kanban or Scrum board, issue-tracking tools such as Jira can make it easier to manage a backlog, especially with a distributed team. But these tools are more complex to use and can add their own overhead to the process. You need to keep things simple.

Project managers recommend how much should be invested to address various risks based on their understanding of project context, but the final decision about what to do and when those efforts are sufficient belongs to the sponsor. Risk management requires executive input, so sponsors need to see all risk data you have.