To me, testing has always been a plan-then-do activity. My chapter in How to Reduce the Cost of Software Testing (Amazon, Barnes and Noble, etc.), outlines what it takes to be ready to test when the software is ready to be tested. Yes, it takes a lot of planning but it pays off in efficiency and enhanced ability to meet deadlines. Below are some of the activities I've performed on projects as a Business Analyst, Test Manager, Developer, Tester or UAT mentor.

• Provided systematic leadership, training and facilitation in the generation of solid test strategies, standardized templates, test plans, test scripts, detailed test conditions, test data requirements, system access, schedules and identification of all UAT testers.
   
• Promoted understanding, acceptance and application of new processes for test management to ensure that all those responsible for test planning were aware of and using the standard approach and templates, and to promote better communication, repeatable processes and common usage of terms, acronyms and tasks.
   
• Developed test plans by interpreting high-level and detailed application requirements. Utilized tools such as Test Director. Developed and executed Alpha tests. Developed a test handbook.
   
• Guided application owners in communicating their test-related requirements for servers, data & network connectivity to ensure these necessary test elements (over and above normal production needs) were included in the plans of those responsible for providing this service.
   
• Coordinated testing activities, ensuring continuous, value-added support for the client and was responsible for the success of 13 testing projects & 10 Senior Technical Engineers & Consultants. Provided oversight, mentoring, and guidance in the execution of consultant obligations. 
   
• Ensured consistency across all projects, facilitated issue resolution, provides status reports to management and otherwise guided test planning activities.
   
• Served as PMO (Program Management Office) Test Methodologist. Developed and implemented overall Test Readiness Strategy. Gathered data regarding current and desired situations. Developed gap analyses and defined test plans. Ensured current situation (test readiness) was understood, future state agreed upon, and test plans developed to implement solutions.
  
• Led Independent *Validation & Verification (IV&V) reviews of testing projects. This ensured the testing activities were completely and consistently documented to provide evidence of due-diligence efforts and to socialize across all IT organizations the processes necessary to keep all future code compliant. *Validation: Does it meet the need of the client? Verification: Does it comply with the requirements?

• Led PMO Test Team. Initiated planning tasks, evaluated test tools & methodologies, defined responsibilities, scope, scheduling, QA checkpoints, compliance criteria, test scripts & cases, training, and issue management / bug tracking for planners as well as for IT. Dealt with multi-platform testing issues involving main- and mid-frame as well as distributed environments. Provided a consistent and complete road map, templates and processes so that the proper test plans could be created (including planning for data and all test scripting), test tools evaluated and installed (including training in use of these tools), and an issue management process was agreed to and followed.
   
• Guided configuration management planning activities for non-software deliverables to minimize the chaos and risk associated with the constant changes of requirements and, subsequently, test plans. Ensured everyone involved was on the same page and had a good understanding of how the CCB (Change Control Board) process impacts test planning and test case maintenance. This heightened awareness of the impact Change Requests could have on test plans and scripts and to ensure lines of communication were open between those approving changes and those test planners that needed to know changes were underway.