[ISTQB] 6.3 Introducing a Tool into an Organization (K1)

LO-6.3.1 State the main principles of introducing a tool into an organization (K1)

The organization must be ready to introduce, use and be involved in adapting the tool through its test processes: only an assessment of the organizational maturity could prove its readiness by clearly identifying the strengths, weaknesses and opportunities to do so. 

Essentially, the assessment should identify which testing area or processes can be improved by adopting the tool. 

LO-6.3.2 State the goals of a proof-of-concept for tool evaluation and a piloting phase for tool implementation (K1)

During test tool evaluation phase, we should identify whether:
- it performs effectively within the software under test and within the current infrastructure.
- it requires any potential changes. 

We should also evaluate the vendor (support, version, reference site visit, training), evaluate internal requirements such as training needed and estimate a cost-benefit ratio based on a concrete business case.

Once the assessment done and the decision to introduce this tool is made, a pilot should be planned for learning more details, confirming that our assumptions were justified (costs involved, benefits, changes identified) and mastering its use before further roll out. 

LO-6.3.3 Recognize that factors other than simply acquiring a tool are required for good tool support (K1)

For successfully deploying a tool within an organisation, the initiative should always follow these principles: 

• roll out the tool to the rest of the organization incrementally.
• adapt and improve processes to fit accordingly to how the tool should be used.
• provide training and coaching/mentoring for new users.
• define usage guidelines.
• implement way to gather usage information.
• monitor tool use and benefits.
• provide support to the test team.
• gather lessons learned from all teams.