Are the customers complaining about the issues in the product/software you delivered? Does your quality team reported similar issues, then it appears your development/product team is not serious about quality teams inputs?
Problem
With agile process in place there are no big QA teams ( just like we see in other models) in the teams. However, with shorter span for potential deliverables, engineering teams usually overlook the issues raised by QA or agile teams. QA teams usually raise issues/bugs, points out design flaws in the product from end-user point of view, but they might be taken low priority from engineering teams which again might be a big concern from customer Point Of View.
Above issue can be a serious problem with startups as they might want to keep their customers/prospects happy with the product/software quality.
- Listen to QA: Listen to QA and Evaluate all the bugs from Quality Team and ensure those issues are addressed before product is released for General Availability.
- Ensure Continuous Bug Fixing: Agile/Process tools will help in tracking issues and prioritizing the bugs/issues. Ensure there is a continuous fixing of bugs/design flaws are handled.
- Act Before Your Customers: QA Teams should be given time to discuss about issues and ensure those issues are addressed before customers/prospects identify them.
How QAmplify helps
QAamplify helps early startups and companies improve QA collaboration within Dev-engineering. Our advisory consultants has very good experience in identifying these QA and development gaps before product/software is shipped for general availability releases.