Collaborating with your team to reach your goal of software that works

“Our company faced material challenges when accommodating growth. New employees, old processes, and looming deadlines combined with a talented and overachieving workforce created what seemed to be insurmountable obstacles. Kevin brought the proper presence, analysis and employee relationship building required to sift through the challenges and identity the high impact/low effort changes we needed to simplify the path forward.  Then in working with our team, we were able to create simplified goals that we could execute to and measure.  This allowed for incremental progress and a defined path forward.  Kevin has the right demeanor and experience to help provide meaningful consultation to produce short term results with clear direction on how to ensure continued success.” — Chris Roussel, CEO Myriad Development

Client Stories

A financial institution had a 4 week mandatory regression test cycle for any change made to their website.  Understandably, financial institutions have low tolerance for risk; however, this made it difficult and costly to implement any new features.  QA Sherpa worked with the team to introduce risk-based testing so the team could focus their testing efforts on the specific areas of risk for a given change.  The end result was higher quality software with much less testing effort and cost.

A data-intensive large software project was spending a large amount of time on testing results and still missing many bugs.  QA Sherpa identified a way for users to quickly enter expected data sets for an automated test.  This quickly and efficiently found errors with each change and involved the key users throughout the project.

A department in a large company lost confidence in an understaffed technical test team due to production bugs, and built their own user-centric test team.  The two teams had a distrustful relationship, duplicated all testing, and continued to have quality issues.  QA Sherpa worked with the teams to collaborate and view the technical and user testers as one extended team.  The result was better, more complete testing, improved team morale, and software that worked.

Scroll to top