A Quality Plan describes per team or project what, where and how to detail features, user stories and requirements and what to test, what to automate, which test techniques to use and how to register the test cases and test results.

As each team and each asset is different, there is no 'one approach fits all' available. Therefor each team will be inventorized what the characteristics of the different assets are and which approach fits best for that team.

Per team an assessment will be executed, where amongst others the following questions will be asked:

• What are the characteristics of the assets: UI, API, 3rd party connection, data, etc
• How often will the asset be updated: can range between each year or hardly ever
• How complex is the functionality
• What documentation is available (GSP, taxanomy, external API documentation, information from the tax authorities)
• What is the expertise and experience of the team
• What is the current approach for describing/detailing User Stories
• What is the current approach for describing test cases and test results
• What is the current scope and approach for automating tests
• What is the current location for storing the information
• What is the current approach for DoR and DoD and what are the criteria

Based on the answers a Quality Plan will be created with:

• What is the preferred approach for describing/detailing User Stories
• What is the preferred approach for describing test cases and test results
• What is the preferred scope and approach for automating tests
• What is the preferred location for storing the information
• What is the preferred approach for DoR and DoD and with which criteria
• What else is required for the team to deliver qualitative features