Agility is something that could start with your developers, but inevitably it will start bringing other areas of the enterprise into its purview - portfolio management, project funding, etc.
One of these areas is #QA. A number of #agile teams continue to use QA as "the folks who manually test things that the developers say are done."
But both the technical and workflow agility enablers you have access to make this a pretty anemic way to use QA.
This post was inspired by a long conversation I had with one of our clients who is just starting to form a QA practice.
If you've wondered or struggled with how QA fits into a more agile flow, I share some thoughts on QA that might help you out.
Traditionally, QA has been synonymous with manual testing and has been established as its own post-development phase. But in an agile landscape, that setup can lead to bottlenecks and silos. That's why we advocate for making QA a strategic player throughout the entire development journey—not just at the end of development.
Tune in to gain insights on reshaping QA practices and maximizing its impact on the entire value stream of software development.
Episode link in the comments or find Agile Bites on your favorite podcast platform.
#agile #QA #qualityassurance #softwaredevelopment #softwareengineering
Principal QA Engineer | 10+ Yrs Experience | Agile & QA Leadership | Enhances Product Integrity through Innovative Quality Solutions | Manual & Automated Testing | Training Cross-Functional Team Builder
4moWell said Natalie. Great job with explaining the importance of QA