What is our overall test strategy for this test phase?:
- Create WBS
- Preparation Plan
- Test Strategy
- Scenarios, Checklists, and Charters
- Execution Schedule
- Human Resources
- Test Execution
- Close Project or Phase
Our Charter for the project defines that we will be running a User Acceptance Test phase. We now need to determine our approach to the finer details of that test phase and will be including those approaches in our Test Strategy. I find it easier to break this down into the various Knowledge Groups to ask the questions – how will we approach our Scope? How will we approach our Communications? How will we approach our Human Resource requirements? Where will testing take place? And so on.
For key headline decisions such as where testing will take place and how we will be deriving scenarios we can start with a high-level workshop with key test team and project and business stakeholders, to run through each of the knowledge areas and brainstorm to identify possible solutions, risks and issues, and potential blocking points. For more targeted decisions such as the test environment we can host smaller meetings with specific teams (in this case, with PMO, Basis, Architecture, and perhaps Data and Development).
All of our various approaches, taken together, form our Test Strategy. They become inputs into our key deliverables and structure the way that we will be doing things and who will do them. Once the strategy is finalised, we need to communicate this to the relevant stakeholders both within and outside the project. Similar to the plan we may need to condense the salient points into a smaller briefing, and host workshops, meetings, or web conferences to communicate the strategy to various parties.
|Previous Page - Define Activities - Preparation Plan||Next Page - Define Activities - Scenarios, Checklists, and Charters|