### 7.2.3 Test Plan A Test Plan defines the goals/scope/objectives of tests, the targeted items, the approach to be taken, the resources required, and the deliverables to be produced. It specifies the universe of tests to be performed (e.g. unit tests, regression tests, functional tests, integration tests, user acceptance tests) as well as the stages in which tests will be executed (e.g. development, integration, test, acceptance). Testing techniques, metrics and criteria used to assess the test results and test completion are also detailed. The main purpose of having a Test Plan is to outline and communicate the testing efforts for a given schedule. Every Test Plan forms the framework within which the Agile Team Members (ATeM) performing the testing will work for the given schedule. By directing, guiding and constraining the test effort, the plan focuses on the necessary deliverables and communicates the effort's intent to stakeholders. Therefore, a Test Plan should avoid details that would not be understood, or would be considered irrelevant by the people involved in the testing activities. Because different levels of tests focus on several areas of functionality and risk, other organisational units may possess various responsibilities regarding the overall testing efforts. Detailed test plans are then necessary for distinct organisational units to plan, prepare, execute, and report testing without increasing risk. | Key Participants | Description | |:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Team Coordinator (TeCo) | Supports the drafting of the Test Plan. Ensures alignment with the project- level Project Handbook, in close collaboration with the Project Manager (PM). | | Agile Team Member (ATeM) | Responsible for drafting the Test Plan, while providing technical advice regarding the testing activities, the scope and type of testing, testing techniques, etc. | | Architecture Owner (ArOw) | Supports by providing technical advice and identifying technical constraints that may impact the testing activities. | | Product Owner (PrOw) | Supports providing insight and information related to the requestor organisation’s reality that may impact the testing activities. | | [[Project Manager (PM)]] | Accountable for how the Agile Project Core Team (A-PCT) plans to address the Testing aspect of the project.<br> Also ensures the alignment of the testing efforts with the overall management of the project deliverables’ acceptance. | **Guidelines** - **Define a Global testing strategy** - Generate an outline of a Master Test Plan early in the project. Testing efforts should not be seen as extra-work to be done but rather incorporated within the development cycles (iterations, releases) as routine work. - **It’s a team effort** – Just because it’s a Test Plan, it doesn’t mean it’s the “ Testers’ responsibility”. Discuss the test mission with the entire Agile Project Core Team (A-PCT). After gaining initial agreement on the test mission, goals, and specific objectives, define the test approach by outlining this information in the Test Plan. - **Align with the Development Handbook** – When defining the global testing strategy, make sure that it’s compatible with the development strategy described in the Development Handbook. - **Focus on the communication aspect of the testing efforts** - Testing may include many different stakeholders at different moments and it is important that everyone understands the testing approach, namely the expected involvement of the stakeholders during the testing efforts. - **Find the right balance** - Review the Test Plan and all related elements with all stakeholders to obtain agreement. Focus on finding a balance between the testing resources and the scope of the current testing effort, based on the identified risks and priorities. - **Document testing risks and contingencies for risk mitigation in the Test Plan** - If project specific risk planning is part of a more significant risk management effort, coordinate testing risks with the risk analysis, design, and mitigation processes of the Project Manager. Ensure that test-related risk items are accurately traced back to requirements and testing assets. ![[7.2.3 Test Plan — Inputs and main roles.png]]