| Responsibility |
Description |
| Act as sparring partner for the developers |
During the Sprint there is a couple of situations where QA can act as sparring partner for the development team:
- In the Sprint Planning where the criteria for ‘Done’ is defined, QA can suggest or confirm how the development can be tailored to create the needed evidence of Good Engineering Practice for verification and validation in the most effective and efficient way.
- When the solution is being created, QA can be take part in the discussion about adopting the development process to individual User Stories, to avoid overdoing verification and validation.
|
| Participate in the Sprint Review |
In the Sprint Review QA has the responsibility to verify the quality of the product and the associated verification and validation documentation.
It might be possible to sign off on a Minutes of Meeting from the Sprint Review and use that as input to the final validation documentation. |
| Perform Quality Surveillance |
Quality Surveillance is an informal process, where QA participate in a “pair programming” session with a developer. There are two goals with this session:
- First it gives the QA an impression of the adherence to the QMS and
- Second it provides input to where the QMS could be improved or tailored to be more useful for the people using it.
|
| Perform internal and external audit |
Audit is a formal process of verifying the adherence to the QMS and is performed both internally and externally. The audit follows a well-defined plan and process.
External audit is typically performed as part of selecting a supplier or as a follow-up on an existing supplier. |
| Improving the Quality Management System |
The QMS is the organisations “script/cook book” for running the business including development. This has to be kept up to date and provide the users with effective and efficient “recepes” for how to do things. QA plays an important role in the process of improving the QMS based on knowledge about the current process and be on the lookout for better methods from e.g. standards, konferences, litterature, etc. |