Key challenges in “quality at speed” software delivery, while keeping costs low

1. Feature not meeting the customer’s need , due to Improper requirement / missing requirement / gaps in requirement specification
2. Dev team re-working on feature due to misunderstanding in requirements.
3. No proper maintenance of test scripts.
4. Dependent more on manual testing for regression.
5. Detection of issues instead of preventing them.
6. QA env blocker issue due to bad builds.
7. Lack of Regression/automation, causing issues in Prod env.
8. No test data in lower env.
9. No shift left in security testing.
10. No shift left in performance testing
11. Manual effort for non-automatable cases.
12. Thinking of automation as a “one-time activity”.
13. “Automate when QA is free” mindset
14. No testing/monitoring beyond prod deployment.
15. Long gap between QA deployment and Prod deployment due to the unavailability of complete automation
16. No involvement of the QA team during the ideation and requirement collection & analysis phase.
17. No sufficient Roll-out testing.
18. Not much collaboration between Product and QA.
19. Running full regression when not required. Like for hot fixes, mini-releases, and feature releases.
20. Not considering automation as part of DOD.
21. Not considering during sprint planning
22. Not Aiming to automate the feature after a round of manual testing.
23. No test after merging builds to the develop branch.
24. Less cross-browser and cross-device testing.
25. Not utilizing CI-CD.
26. Missing test case review meeting / PR review meeting.
27. No stage/UAT environments.
28. No ‘budget for maintenance’.
29. No budget for paid tools.
30. Human errors