Failing to know the state of your QA
You’ve probably seen it happen: QA gets pushed to the final sprint when deadlines loom. But teams embedding quality checks during feature planning cut bug escape rates nearly in half. This shift from reactive testing to proactive risk-spotting transforms your entire delivery flow. They may literally lack dedicated people to find and report issues, and devs simply have to make sure that software runs at all. This often brings awkward workarounds that are not easy to pinpoint and resolve a few months later.
This video also covered additional QA management issues and the ways to solve them.
Even if you donāt have the resources to fix QA issues at the moment, you need to be aware of them. A few smaller issues may result in a severe defect, and now you canāt trace those smaller issues to do a quick fix. Onboarding QA specialists, once you have the resources, will be a bit frustrating and inefficient when they donāt know quite what to fix and/or which fixes to prioritise.Ā
What you need here is to start listing defects early in an issue tracker solution. You may use a dedicated bug tracker or adopt an Application Lifecycle Management tool that works for both software development and quality assurance. The second approach is better if you pay for a development issue tracker or know that you will have to upgrade anyway.
Proven ALM that saves hours on both development and QA management
Subpar DeveloperāQA communication
Testers are the key part of quality assurance, but there are no real gains without developers that fix discovered issues. Troubleshooting complex issues may require a dev and QA specialist to go over the same defect several times. This gets pretty chaotic if done on work messengers or, even worse, verbally.Ā
Your best option here is to utilise the discussions functionality of the tool that you use for QA problem management. Public communication is how both the people involved and their colleagues can trace the lifecycle of the bug and pick up the mantle if needed. Opting for the issue tracker over company messenger will also help developers focus on non-QA tasks, then come back to a defect when they have the time.
Building Stronger QAāDeveloper Collaboration with 'Three Amigos' and Embedded Teams
Solid QAādeveloper collaboration catches bugs early and cuts down friction. Here’s a tactic that’s proven effective: the ‘Three Amigos’ meeting.
Before any coding starts, bring together the product owner, a developer, and a QA specialist to quickly align on acceptance criteria and edge cases, think 15 minutes, not an hour. Instead of treating QA as the final checkpoint, embed QA directly into your development squad. This shift makes quality everyone’s job from story kickoff through release.
Developers start writing better tests when they’re working alongside QA daily rather than throwing code over the wall. Start simple: try one ‘Three Amigos’ session this week for your next user story and watch how much clearer your requirements become.
Measuring progress
Improving quality is a noble goal, but it is also hard to tell whether you are succeeding at something so vague. Did you improve the quality by squashing some UI bugs that didnāt affect functionality but were very noticeable? Was fixing a potentially critical issue a good way to apply the effort if the problem never occurred?
You need meaningful QA metrics that actually move the needle. Track deployment frequency, change failure rates, and defect escape rates. These three give you real visibility into whether your testing process supports rapid, quality releases. Companies using these focused metrics see quality improvements nearly double within months. You’ll spot bottlenecks fast and can adjust before small issues become release-blocking disasters. Find 11 more ideas in our separate article.
Juggling multiple QA solutions
While your team will likely have just one solution to track QA issues, testers are likely to use additional software in their work. Selenium or Selenium-based solutions are almost always used for automated testing, and then there are test type-specific tools like JMeter or Ranorex. Staying on top of test reports across several tools gets pretty hard.
Our recommendation is to pick an issue tracker that can aggregate input from test automation tools and other QA software. Native integrations with popular tools are convenient but scarce. Most vendors, however, will give you the option to integrate any QA tool via REST API. Ask (and try) before you buy.
Unclear timeline
Every stage of software development requires time. It can, however, be frustrating for stakeholders to see that QA is taking longer than expected ā simply because it is the last hurdle before release. This is how you brew frustration from missing a deadline or deploying an unpolished build, contributing to test management problems.Ā
Formalising the QA timeline would be a great start, but it is even better to visualise it. A lot of modern test management solutions offer sprint planning that you can align with the developerās schedule. Simplified planning is another advantage to adopt an ALM.
Managing Last-Minute Changes to Requirements
Last-minute changes? Yeah, they’re basically standard operating procedure now. But you can handle these curveballs without your team losing their minds. Start by setting expectations upfront. Make it crystal clear that late changes mean trade-offs in test coverage.
When changes hit, rank your tests by risk and business impact first. Skip the nice-to-haves and focus on what could actually break user workflows. Then tell stakeholders exactly what you’re NOT testing before anything goes live. Create a simple ‘change impact’ template that forces requesters to identify what they’re willing to sacrifice. Most people requesting changes haven’t thought through the real cost. Once they see it laid out, they often realise their ‘urgent’ change can actually wait until the next sprint.
Subpar pre-QA builds
With testers ultimately responsible for the quality, developers can get a bit lazy about what they send them. There are cases when they may send obviously flawed code just to move on. This results in extra work for testers, and you also now have to think how to manage QA teamās frustration.
Unit testing is a great solution that will save everyoneās time. Devs can make simple tests to catch obvious flaws early and receive fewer bug reports from the QA team. Testers wonāt have to nudge devs for simple fixes and have more time to go over less obvious potential problems.
Unactionable bug reports
Bug reports wonāt always come out perfect even if you have a good culture for making them. New team members will need time to soak it in. Non-technical stakeholders or even external people with occasional problems will probably not abide either. Incomplete bug reports make your team spend extra time reproducing and solving issues.
The best way to make actionable bug reports is to visualise them. One emerging trend is using solutions that can record test execution of a test case or simply take a video of what happens on a userās screen when they have an issue. We recommend trying a solution called Capture to get a glimpse of how great this tech is.
Long idle time
Devs make code, testers find bugs, devs fix them, testers look for more bugsā¦ This is the usual QA flow until testers canāt find any issues that the product team would be uncomfortable to fix at a later stage. The problem is that devs can be waiting for testersā response for too long (and vice versa).Ā
The solution is simple: establish workflows that specify exact QA steps and how long they should ideally take. This will work much better if your test management solution allows you to configure such workflows natively and for example auto-nudge colleagues that are taking too long. Itās often okay that they do, but itās a shame when somebody simply forgets about a ticket assigned to them.
Chaotic test suite
Test management solutions are a great way to formalise your test suite, but you still need a system to follow. It is hard for new team members to navigate tests that have inconsistent naming, while seemingly duplicate test steps are confusing if you want to reuse them somewhere else.
Getting a good naming convention would be a great start to tidy up your test suite. You can go on to define how test steps are created and what testers should write in the description of every test case. Test management solutions can help you here, but the key success factor here is good fundamentals from QA management.Ā
Ever-growing scope
Test automation is a great asset, but it is not the silver bullet. One full run of automated tests can still take up to an hour, and one time wonāt be enough. At some point, there are just too many tests to test too many things.
A modern answer is artificial intelligence. You can use AI-powered test management solutions to optimise your existing test suite or enlarge it faster than human testers ever could. You will find such features in tools from both long-time and emerging vendors.
Proven ALM solution with AI test generation and prioritisation
