Following list of process/steps would definitely help to improvise the current stage of the application especially when your team is planning to take over the project from different company.
Split the test process into two phases, First Phase consist of identify/uncover the issues which are currently exist in the system. Second phase consist of Retesting of ...
Your project sounds like where my project was when I started. You need to maintain your discipline. Here are the mistakes I've made, the lessons learnt, and what I've improved:
It's easy to think "I'll remember bug X", or "I'll do it later", but in reality you'll be overwhelmed and forget. Use a bug tracker, and record each bug as soon as it's discovered! ...
Context: So recently I was on a project as a consultant, to help improve reliability and scalability (fix bugs and make it go fast). I turned around their product, with a 800% performance increase and 70% reduction in errors.
These are the biggest takeaways I have from that:
Add a Real User Monitoring (RUM) and Error Monitoring tool.
I used raygun.io I ...
best practices on how to start the improvement strategy?
what processes/tools would be the best?
Nobody will be able to give a precise answer for this, because the value of any practice depends on its context.
some ideas on how to start the improvement strategy?
As said above, you will need to understand your context in order to evaluate the value ...
Start with understanding what works:
What data is valid ?
What data is used ?
What is successful ?
What are the variations ?
What are the users like ?
What are the long term business goals ?
What are the short term business goals ?
Goals can be very different across industry, company stage, location, profit vs non-profit, etc. Learn what quality means to ...
I think the article you link confuses two different things- bug tracking system is not the same as the bug handling process.
Saying "If it is non-critical, you drop it." doesn't mean you don't track the things you are leaving, tracking can be done in using any system you like and in this case it's the Kanban board. The opposite is also not true, you can ...
The removal of bug tracking doesn't mean the removal of bugs !
In fact the ability to find and spot bugs (your skills) are more important and timely than ever.
It can feel very comforting to log bugs. They prove (validate) that you found stuff. They add to a mountain of work that needs to be done. See that backlog grow! Unfortunately we're moving away ...