As the SRS / Functional spec. begins to stabilize, usually post Draft 2, QA then produces work while other become the reviewers.
Write Test and Configuration Management Draft 1
(this document identifies primary test equipment setups, specifies resources,determines how progress will be reported, links to other QA docs such as glossary, automation plans, work flow, etc)
Review Test and Configuration Management Draft 1 (DEV, Prod Mgr, Corp Quality, others)
Design New Test Cases (Cycle 1)
Review New Test Cases (DEV, others)
Update Test Cases (QA)
Review and Update Existing Test Cases (QA)
Test Case Design Complete Milestone
Create Planned Testing
(select test cases and corresponding setups assigned to testers) --- this is your 'Planned Testing" (not to be confused with Test Plan which depicts all possible testing) and we'll just call them Test Sets for ease of reference. This is your based line for planned vs. actual metrics.
Test Set 1:
Test Set 2:....etc.
Planned Testing Approved
Write Automation Spec. Draft 1 (QA)
(this document identifies how testing will be automated -- what framework will be used, what scripting language, where repository will reside, what hardware setups will be used, how where and when results get reported etc.
While QA is doing this work, Development is off coding, creating unit tests, and creating a build schedule that shows what will be delivered when, up through Functional Complete (all new functionality coded)