Building the Test Team and Testing Competencies
This domain examines how you structure a test team, assess and develop competencies, and keep people motivated. Exam questions tend to focus on role differences, centralized versus decentralized organization, and evidence-based development planning.
Roles and competencies
ISTQB defines test manager, test analyst and technical test analyst roles, but titles vary by organization. Competencies span testing knowledge, technical skills, business domain knowledge, analytical ability, communication and interpersonal skills. A skills matrix records current proficiency against required proficiency; the gap drives training, coaching, mentoring or recruitment. T-shaped team members have broad testing awareness plus depth in one area.
Organization and motivation
Centralized teams (test factory, independent test group) offer consistency, reuse and independence but can lose project context. Decentralized teams stay close to the product but may duplicate effort and weaken independence. Use Tuckman's stages (forming, storming, norming, performing, adjourning) when planning team development. Motivation is intrinsic and extrinsic; Herzberg separates hygiene factors from motivators, so bonuses alone rarely sustain quality. Training, communities of practice and certification support development but do not prove competence.
Worked example
A team has two junior testers, one senior automation engineer and no domain expert. The skills matrix shows gaps in non-functional testing and payments knowledge. The plan pairs juniors with the automation engineer, assigns a payments subject-matter expert as reviewer, funds one analyst's performance-testing training, and uses exploratory sessions to build business knowledge. Reasoning: development is matched to project risk, internal mentoring is used before external hiring, and domain knowledge is validated rather than assumed.
Traps
Do not equate certification with competence. Do not rely only on extrinsic rewards. Do not assume a centralized team guarantees independence. Do not skip team-development stages when planning.