Analysis of software requirements and existing QA process

A QA consultant analyzes functional and non-functional software requirements to get an understanding of the project’s scope and software specifics to outline a path for establishing the QA process. In case the QA process is already established, a QA consultant analyzes it, evaluates the QA maturity level, points out QA flaws (e.g., tests planning and scheduling problems, management problems), and outlines a path for the QA process improvement or redesign.

QA process (re)design

• Reviewing functional and non-functional software requirements to improve their consistency and completeness for the development process and future testing activities. Creating requirements traceability matrix.
• Analyzing potential risks (e.g. tight timelines, changing requirements, etc.) and creating a risk mitigation plan.
• Planning regular and systematic design reviews to spot logical errors and start creating a test plan earlier.
• Taking a shift-left approach to testing and moving testing activities closer to the beginning of the software development process.