TOGAF EA · Scenario technique

How to Read a TOGAF Practitioner Scenario Without Getting Lost

Before you compare the answers, turn the scenario into five things: the problem, the ADM context, the stakeholders, the constraints and the decision required. That gives you something concrete to test every option against.

It is easy to reach the end of a Practitioner scenario remembering the company, the project and a dozen TOGAF terms, but still be unsure what you have been asked to decide. Reading it again from the beginning may leave you with the same problem.

Try changing the purpose of the first read. You are building a brief for a decision. You need enough context to explain what matters now, what has already happened and what a useful response must accomplish.

The five-part brief

  1. Problem: what needs to change or be resolved?
  2. ADM context: what architecture work is happening, and what has already been agreed?
  3. Stakeholders: whose concerns and decisions matter?
  4. Constraints: what limits an acceptable response?
  5. Decision required: what exactly must you recommend, explain or do next?

This is a study technique, not an official Open Group answering formula. Practise it until you can form a short mental brief without writing out every field.

Start with the request, then read for evidence

Glance at the final request before reading the scenario closely. Find the specific task: recommend an approach, address a concern, select an activity or identify what should happen next. A generic instruction to choose the best answer is not the task by itself; look for what the architect has actually been asked to address.

Then read the full scenario. Knowing the request gives you a reason to pay attention to particular details. A sentence about an unhappy operational manager matters differently when you are choosing a communication approach than when you are assessing an implementation change.

Do not commit to an answer from the final sentence alone. It tells you what to look for. The scenario supplies the conditions your answer must satisfy.

Extract the five things that change the decision

1. State the problem as a gap or tension

“The company is modernising” is background. “Two divisions disagree about the outcome the architecture must support” is a problem you can act on.

Ask what is unresolved. Is the issue unclear scope, competing stakeholder concerns, a gap between baseline and target, implementation conformance or a proposed change? Keep the wording close to the facts. Do not add a root cause that the scenario never gives you.

2. Locate the work in its ADM context

The Architecture Development Method (ADM) gives you context for the work. Look for activities and the status of deliverables: requested, being developed, reviewed or approved. “A migration plan exists” tells you less than “the migration plan has been approved and implementation has begun”.

If a phase is named, use it. If it is not, infer the relevant activity from the evidence and keep that inference provisional. A familiar term can appear in several parts of the work; a stakeholder concern alone does not prove that the scenario is in Phase A.

Do not force every question into a single phase. The Open Group says a scenario may combine multiple syllabus areas. Requirements, stakeholder management and supporting techniques can matter alongside the phase-specific activity.[1] Treat sequence as something to justify from the situation; a return to earlier work is not automatically wrong.

3. Connect each stakeholder to a concern

Remembering job titles is less useful than remembering what each person needs. The sponsor may need a clear business outcome; operations may need continuity; a business unit may need a concern represented before it can support a proposal.

Also notice the role you are playing. Are you advising, analysing, seeking agreement or exercising an authority explicitly given to you? An option that assumes you can approve something may be weaker if the scenario only asks you to make a recommendation.

A short pairing helps: operations → service continuity; sponsor → agreed outcome. That is easier to use when comparing options than a list of names.

4. Separate limits from preferences

Find the facts an acceptable response has to respect: scope, agreed principles, legal obligations, deadlines, available resources or a stated decision process. Notice limiting words such as must, only, within and not yet.

A manager wanting a quick answer is not necessarily permission to ignore governance. Equally, do not invent a policy, budget limit or mandatory approval that is absent from the scenario. Distinguish what is stated from what you would normally expect at work.

5. Restate the decision in one sentence

Finish with a sentence such as: “I need to recommend how to resolve the competing concerns before the architecture scope is approved.” If you can only say “this is about stakeholder management”, your brief is still too broad.

The sentence should tell you what a strong response must achieve. It becomes your filter when several options use the right vocabulary.

Separate background detail from decision-changing evidence

Some details establish the setting without helping you choose a response. In the eight original scenarios in ArchitectCertPrep’s free paper, for example, the supplied answer rationales remain supported when the exact company employee totals are removed.[4] That is an observation about this practice paper, not an official rule about exam construction.

It helps to think of “noise” as background for this particular request. A detail can matter in one question and add little in another. Read the whole scenario once, then use this check when a detail is pulling you into a side investigation:

Keep it or set it aside?

  1. Connect it. Does it affect the requested outcome, scope, current stage, stakeholder concerns, authority, constraints, risks or dependencies?
  2. Try removing it mentally. Would the task, an acceptable response or your reason for preferring one option change? If so, keep it.
  3. Park it provisionally. If you see no connection, continue to the answers. Revisit the detail if an option makes it relevant or your two leading choices remain tied.

You do not need a hidden explanation for every fact. If nothing in the request or options makes a company’s founding year relevant, do not spend time inventing a link. Keep the original scenario available rather than trying to erase the detail from memory.

Be more careful with facts that appear to be background but explain a concern: an earlier failed implementation, a stakeholder’s objection, a regulatory obligation, a deadline or an approved decision. These can distinguish two otherwise plausible responses. Familiarity with the industry is not a substitute for reading the stated conditions.

This is a light check for distracting details, not a second analysis exercise for every sentence. When relevance is uncertain, retain the fact and move on; compare the options before spending more time on it.

A worked example: from story to decision brief

Original teaching example. This is not an official exam question, and the comparisons below are not official answer scores.

Scenario

A services company, founded in 1987 and employing about 9,000 people, has asked its architecture team to develop an Architecture Vision for a shared customer-service capability. The Request for Architecture Work covers two divisions. One division wants a single customer view; the other prioritises continuity for its existing service teams. The sponsor wants an agreed scope before authorising the next stage of architecture work. A director proposes choosing a software platform immediately to keep the initiative moving.

Your task: recommend how the architect should address the competing concerns so that the scope can be agreed.

ExtractWhat the scenario tells you
ProblemThe divisions want different outcomes, and the scope is not agreed.
ADM contextArchitecture Vision work: Phase A is the relevant starting context. Further architecture work awaits authorisation.
StakeholdersBoth divisions have concerns; the sponsor needs agreement on scope.
ConstraintsThe request covers two divisions. Scope agreement comes before authorising the next stage.
Decision requiredRecommend an approach to the competing concerns that supports agreement on scope.

Apply the relevance check here: removing “founded in 1987” and the exact employee total changes neither the task nor the reason for preferring a response. Set those details aside. Retain the two divisions, their competing concerns and the authorisation condition: they define the problem and what must happen before the next stage.

The director’s software suggestion is worth retaining too. It is not the requested outcome, but it makes a premature solution choice tempting. A detail that helps you reject an option is relevant even when it does not belong in your final recommendation.

Before reading any options, you can already predict the kind of response you need: work with the relevant stakeholders to clarify and reconcile the required outcomes, make the implications visible in the vision and proposed scope, and seek the necessary agreement. You do not need to predict the exact wording.

Now compare the responses against the brief

Clarify both divisions’ concerns and agree the scope with the relevant stakeholders.

This directly addresses the unresolved issue and the sponsor’s condition. The detail would still need to match the full question, but its purpose fits the brief.

Record the concerns and circulate the existing proposal.

Recording and communicating can help. On its own, this response does not explain how the competing needs will be resolved so that scope can be agreed.

Compare software platforms and select the most flexible product.

A flexible product may sound helpful, but this changes the task to solution selection while the intended outcomes and scope remain unresolved.

Remove the second division from scope to simplify approval.

This avoids a concern by changing the scope of the request without an agreed basis. It does not satisfy the stated task.

The important difference is the link between the action and the unresolved decision. The strongest-looking response is not stronger because it is longer or contains more TOGAF terms.

Change one fact and the evaluation may change. If the divisions had already agreed the scope and the request were now to assess a technology option against approved requirements, repeating scope discussions could miss the task. Read what has been completed as carefully as what remains to be done.

When two answers still look almost identical

Compare the exact difference, then return to the scenario fact that makes it matter. Look for changes in the proposed action, sequence, scope, stakeholder involvement or assumed authority. Do not reread four long answers as four undifferentiated blocks.

A useful tie-break sentence

“I prefer this response because the scenario says ___, and the alternative would ___.”

If you cannot fill those blanks, check whether you have missed a condition or whether you need to confirm a TOGAF concept. “It sounds more comprehensive” is weak evidence. An answer can be detailed and still solve the wrong problem.

For OGEA-102, the four responses carry 5, 3, 1 or 0 points, and you select just one. You do not submit a ranking of all four.[1] Comparing the alternatives is a way to make that single selection more deliberate. For the scoring mechanics, see how gradient scoring works.

Use the reference to answer a specific uncertainty

Once you understand the task, the open book can help resolve a narrow question: the purpose of an activity, the content of a deliverable or the relevant guidance for a technique. Decide what you need to confirm before opening it.

The current Part 2 reference is provided as two PDFs: TOGAF Fundamental Content and the applicable TOGAF Series Guides, accessed through REFERENCE buttons.[2] The PDFs appear in a built-in reader.[3] Practise navigating the relevant material during preparation.

After checking a passage, return to your decision sentence. Finding familiar wording in the book is useful only if the proposed response also fits the facts. If you keep browsing without a specific uncertainty, rebuild the five-part brief.

Practise the reading step on its own

Take an unfamiliar, legitimate practice scenario and cover the answers. Read the request, extract the five things and describe the kind of response you expect. Then uncover the options and compare them against your brief.

After checking the supplied rationale, review three things:

Keep any notes short during study. The aim is to make the reading process dependable enough to use mentally under exam conditions. This method supports your TOGAF knowledge; it cannot supply a concept you have not learned.

For a broader preparation plan, use the TOGAF Practitioner study guide. Here, the immediate exercise is narrower: understand the decision before you evaluate its possible answers.

Try the five-part brief

Use the next scenario to identify the problem, ADM context, stakeholders, constraints and decision required. Then explain which fact makes your chosen response stronger than the nearest alternative.

Try the free paper

Official sources

Exam details checked on 26 October 2026. The reading method and teaching example are editorial guidance.

  1. The Open Group — OGEA-102 Part 2 exam plan: scenario format, single-answer selection, gradient scoring and integrated syllabus coverage.
  2. The Open Group — Part 2 open-book contents: the two reference PDFs.
  3. The Open Group — reference-book display: the built-in PDF reader.

Practice example source: ArchitectCertPrep’s free paper, eight original scenarios. The background-detail observation is an editorial comparison of the scenarios, options and supplied rationales; these are independent practice materials, not official Open Group items.