PRINCE2 Themes
What the themes are
The seven themes describe the aspects of project management that must be addressed continually: Business Case, Organization, Quality, Plans, Risk, Change, and Progress. Each theme answers a question - for example, Business Case asks "why?", Organization asks "who?", Quality asks "what are the quality requirements?", Plans asks "how, how much, when?", Risk asks "what if?", Change asks "what is the impact?", and Progress asks "where are we now, where are we going?".
What you must understand
For each theme know its purpose, the key roles involved, the management products produced, and how it is applied at each process level. Quality uses a quality strategy, quality criteria, quality register and quality review technique. Plans distinguishes project, stage and team plans, and knows product-based planning (product breakdown, product descriptions, product flow diagram). Risk uses a risk management approach and risk register, with cause–event–effect thinking. Change covers issues and change control, including the issue register and change budget. Progress relies on tolerances, checkpoints, highlight reports, end stage reports and lessons logs.
Traps in questions
Common confusions: the Business Case theme produces the Business Case and benefits management approach, but the principle is continued business justification. The quality register vs. the issue register; the lessons log vs. the lessons report. Risk owners vs. risk actionees. Also watch for options that place a theme's activity in the wrong process, or that treat themes as one-off documents rather than ongoing activities.
Rule of thumb
Map each management product to its theme and the process that creates or updates it. If an option names a product, ask: which theme owns it, and who is accountable?
Worked example: A team identifies a potential supplier delay. It is recorded in the risk register with an owner and response; if it materialises, it becomes an issue in the issue register. Same event, different theme.