CTAL-TM v3.0 study plan

Before you start the CTAL-TM study plan

This is an adaptable six-week plan for Test Management v3.0. It is our editorial schedule, not an ISTQB-required preparation period. Start with roughly five to seven focused hours a week, split into short sessions and one longer exercise. Extend the plan when experience or practice shows that you need more time.

Make defensible decisions about testing priorities, evidence, resources and people.

• Confirm your eligibility in the exam overview and with your intended provider. Preparation does not replace prerequisite evidence.
• Save the current syllabus and the matching sample question and answer files. Keep at least one sample unseen until you are ready for a meaningful timed check.
• Make a learning-objective tracker with columns for objective, confidence, evidence and next action.
• Choose a small fictional product or project for worked exercises. Avoid using confidential employer material in public notes.

Your six-week schedule

Move on based on the output, not simply because a calendar week has ended. Each week includes reading, worked practice and review. A course or previous experience can change the pace, but should not leave gaps in the current objective list.

Week 1: establish the management context

Begin chapter 1. Describe a release, its stakeholders and constraints. Prioritize product risks and derive a project test approach. Keep product risks separate from delivery problems such as missing staff or environments.

Finish with: A context sheet, stakeholder map and risk-based approach.

Week 2: monitor, control and improve

Continue chapter 1. Invent progress data, choose measures for two audiences and practice a control decision when the release slips. Propose one process improvement with evidence that would show whether it worked.

Finish with: A dashboard explanation, control action and improvement experiment.

Week 3: estimate and handle defects

Read chapter 2. Estimate a defined set of testing activities, recording assumptions and dependencies. Design a defect workflow and identify what happens when teams disagree about impact or priority.

Finish with: An estimate with assumptions and a cross-team defect workflow.

Week 4: build capability and a business case

Work through chapter 3. Compare needed skills with the team’s current capability. Plan a development action and explain its trade-offs. Draft a business case that distinguishes prevention costs, failure costs and expected benefits.

Finish with: A capability map and a concise testing business case.

Week 5: practice with sample set a

Complete the remaining objectives and attempt official set A without the answers. Use its answer file to review reasoning and point allocation. Check your score against that set’s instructions rather than assuming every file has the same total.

Finish with: An objective-based error log and a remediation list.

Week 6: test fresh reasoning with set b

Repair weak areas, then use the previously unseen official set B as a timed check. Rework wrong and guessed answers with changed constraints. Use the current rules and your provider’s approved duration for the actual booking.

Finish with: A fresh practice result, explained corrections and a booking checklist.

Use a repeatable study session

1. Recall: spend five minutes explaining the previous topic without opening your notes.
2. Read: select a manageable set of objectives and clarify unfamiliar terms in the official glossary.
3. Apply: produce a trace, model, plan or decision appropriate to the topic. Show assumptions and working.
4. Review: compare your result with the syllabus or official sample explanation and log the gap.
5. Retest: revisit the gap later with changed values or constraints.

You can spread these activities across sessions. Keep the practice output small enough to review properly. A large unfinished framework or document can hide the exact concept you need to learn.

Fix weak areas deliberately

Use an error log with the objective, your answer, the missed constraint, the correct reasoning and a new practice task. Separate knowledge gaps from misreading, calculations and time pressure. Correct answers chosen by guessing should still enter the log.

• Watch for: Quoting the older 86-point structure instead of checking the current 88-point rules.
• Watch for: Treating a percentage complete as evidence that important risks are covered.
• Watch for: Selecting a management action without considering stakeholders and constraints.
• Watch for: Turning an estimate into a promise while hiding its assumptions.

If you repeatedly miss the same type of decision, stop taking full mocks for a session. Rebuild the underlying example, explain it aloud and then try a different problem. A memorized repeat score is revision evidence, not an independent readiness result.

Check readiness before booking

• You have reviewed every current learning objective and can produce evidence for the difficult ones.
• You can explain why plausible alternatives fail under the scenario’s constraints.
• You can use the official sample exam instructions, point allocation and timing without assuming all questions carry equal points.
• Your repeated practice results are interpreted honestly: first attempts and familiar repeats are recorded separately.
• Your provider has confirmed prerequisites, language, duration, any adjustment and the complete fee.

No checklist predicts a pass. If you still rely on remembered sample answers, use an extra week for targeted exercises. When ready, follow the booking checklist and your country guide.