ISTQB CTAL-TM study materials
ISTQB CTAL-TM study resources

ISTQB CTAL-TM study plan

ISTQB CTAL-TM · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Test Management in Context: Organizational Test Strategy and Test Approach & Test Planning, Monitoring, Control and Reporting

  • Distinguish organizational test strategy from project-level test approach and write a one-page comparison table with at least six discriminating criteria

  • Map the four test strategy drivers (risk, business/domain, organizational, project constraints) onto a fictional organization and justify each choice in writing

  • Draft a test policy outline covering scope, objectives, governance and improvement loop

  • Define at least five test metrics you would report to senior management and state the decision each metric supports

Your checkpoint

A 2-page organizational test strategy document for a fictional product plus a metrics-to-decision table with at least 5 rows

Week 2

Test Management in Context: Organizational Test Strategy and Test Approach & Test Planning, Monitoring, Control and Reporting

  • Explain how the chosen software development lifecycle model constrains test planning, entry criteria and exit criteria

  • Derive test approach decisions (analytical, risk-based, methodical, regression-averse) for three contrasting project scenarios

  • Construct a test plan skeleton aligned to IEEE 829-style content covering scope, approach, resources, schedule, risks and exit criteria

  • Critique two sample test plans and list at least four defects in each with the corrected wording

Your checkpoint

A complete test plan for a scenario of your choice plus a written critique of two flawed sample plans

Week 3

Managing Test Stakeholders, Risks and Defects & Test Planning, Monitoring, Control and Reporting

  • Perform a product risk analysis using likelihood and impact scoring on at least 15 identified risks, and rank them

  • Map each top-ranked risk to a concrete test activity and a residual-risk statement

  • Define the risk response options (mitigate, transfer, accept, contingency) and assign one to every high risk

  • Design a risk-based test prioritization scheme that can be applied when time is cut by 30 percent

Your checkpoint

A risk register with 15+ scored risks, each linked to a test activity and an owner

Week 4

Managing Test Stakeholders, Risks and Defects & Test Planning, Monitoring, Control and Reporting

  • Write a defect management process covering triage, severity vs priority, workflow states and root cause categories

  • Explain how defect data feeds test process improvement and release decisions

  • Build a monitoring and control cycle: which metrics trigger which control actions

  • Produce a status report template with progress, product quality, defects, risks and deviations

Your checkpoint

A defect management process description plus a filled-in status report for a mid-project snapshot

Week 5

Building the Test Team and Testing Competencies & Test Management in Context: Organizational Test Strategy and Test Approach

  • Identify the skills and roles needed for a test team given a stated test strategy and product risk profile

  • Write a competency matrix for at least six roles across technical, business-domain and soft-skill dimensions

  • Design a recruitment and onboarding plan including interview exercises that test real testing skill

  • Plan a motivation and recognition approach that addresses intrinsic and extrinsic factors for testers

Your checkpoint

A competency matrix with 6+ roles and a matching onboarding plan spanning the first 90 days

Week 6

Building the Test Team and Testing Competencies & Managing the Test Activities Across the Software Development Lifecycle

  • Create a personal and team training plan based on gaps identified in the competency matrix

  • Explain how tester certification, experience and domain knowledge affect team capability claims

  • Describe how to run a skills assessment that avoids bias and self-reporting inflation

  • Draft a coaching plan for a junior tester over one quarter with measurable checkpoints

Your checkpoint

A team development plan with gap analysis, training actions, owners and success measures

Week 7

Managing the Test Activities Across the Software Development Lifecycle & Managing Test Stakeholders, Risks and Defects

  • Compare test management across sequential, iterative, incremental and continuous delivery lifecycles on planning horizon, documentation and exit criteria

  • Define entry and exit criteria for each of three lifecycle models and test them against a real project

  • Describe how to manage test environments, test data and configuration across parallel iterations

  • Plan stakeholder communication for a distributed team including cadence, channels and escalation path

Your checkpoint

A lifecycle comparison table with entry/exit criteria for three models plus a stakeholder communication plan

Week 8

Test Management in Context: Organizational Test Strategy and Test Approach & Building the Test Team and Testing Competencies & Managing the Test Activities Across the Software Development Lifecycle & Test Planning, Monitoring, Control and Reporting & Managing Test Stakeholders, Risks and Defects

  • Consolidate weak areas by re-testing every domain against the syllabus chapter structure and logging gaps

  • Answer at least 120 practice questions under timed conditions and analyze errors by domain and by error type

  • Rehearse explaining five exam-style scenarios aloud in under three minutes each

  • Build a one-page memory sheet of decision rules, metric definitions and process steps

Your checkpoint

A scored practice exam log with per-domain accuracy and a one-page memory sheet

Milestones

Week 2: You can explain the difference between test strategy and test approach, and produce a defensible test plan for a new scenario without notes

Week 4: Your risk register drives your test plan: every high risk maps to a test activity, and your status report shows at least one control action taken in response to a metric

Week 6: You can justify team composition and a training plan from a competency matrix, and state how you would measure improvement

Week 8: Practice exam accuracy is at least 75 percent overall with no domain below 65 percent, and error analysis shows recurring mistakes are resolved