MD Dev QA Approach
While fully supporting the traditional waterfall process if a project demands it, we do lean heavily towards agile and scrum-based workflows to better mitigate risks, reduce time to market, and deal with changing requirements in a more efficient manner.
Underpinned by our man-years of experience and industry’s best practices, the MD Dev approach emphasizes early testing, predictability, efficient communication, and detailed reporting.
We are also big believers in QA automation, and advocate implementing a test automation strategy whenever it makes sense and benefits the project.
The diagram below illustrates a typical flow of QA activities within an agile iteration or sprint.
Our team uses a well-defined, no-nonsense testing process that typically includes the following steps:
- Choosing the optimum QA strategy
- Choosing the right software tools
- Test or sprint planning
- Setting up the environment and preparing the test data
- Executing tests
- Transferring the QA deliverables
- Conducting a post-project or post-sprint review