Overview
Implementation is 8% of the COBIT 2019 Foundation exam and covers the approach in the COBIT 2019 Implementation Guide. Governance improvement starts when pain points or trigger events create a need to act, and it succeeds only in an environment with sponsorship, clear ownership and stakeholder involvement. The improvement itself follows a seven-phase life cycle, each phase framed as a question: what are the drivers, where are we now, where do we want to be, what needs to be done, how do we get there, did we get there, and how do we keep the momentum going.
Each phase is viewed from three perspectives: programme management, change enablement, which deals with people and behavior, and the continual improvement life cycle. The Design Guide informs the early phases, the business case supports sponsorship, and capability levels from Performance Management measure the gap the program closes.
How it's tested
Questions describe an activity or situation in a governance improvement program and ask which phase it belongs to, which of the three perspectives addresses it, or whether a situation is a pain point or a trigger event. The reasoning is to match the activity to the question each phase asks and to the perspective that owns it.
-
Which phase
An activity such as assessing current capability levels or reviewing whether benefits were realized is described, and you choose the phase, here phase 2 or phase 6.
-
Which perspective
You decide whether a concern belongs to programme management, change enablement or the continual improvement life cycle.
-
Pain point or trigger event
A situation such as repeated audit findings or a new CEO is described, and you classify it as an internal pain point or a trigger event.
A question says a governance team, having agreed the drivers for change, now rates the current capability of priority processes and asks which phase this is. Agreeing drivers is phase 1. Rating current capability answers the question where are we now, which is phase 2. Phase 3, where do we want to be, is the tempting distractor because target levels are often set alongside, but it defines the target rather than measuring the present.
Framework topics 5
Official framework topics from the ISACA outline, in outline order.
8.1 Implementation approach and guidanceHow the Implementation Guide relates to the design and the business.
- What it means
- The COBIT 2019 Implementation Guide describes a practical, continual-improvement approach to governance of I&T, tailored to the enterprise and run as a program rather than a one-off project.
- What to understand
- The Design Guide determines what the tailored governance system should look like; its results feed the early implementation phases on drivers, current state and target state. Implementation must be owned by the business with executive sponsorship, not left to IT alone.
- How it shows up
- A question asks how the Design Guide and Implementation Guide relate, or who should own a governance improvement program.
- Common confusion
- Treating implementation as an IT project, or assuming the Design Guide and Implementation Guide are alternatives rather than complementary.
8.2 Pain points and trigger eventsThe symptoms and events that create a need to act.
- What it means
- Pain points are internal symptoms that suggest governance is weak, such as failed IT-enabled initiatives, rising costs, repeated audit findings, significant incidents or regulatory failures. Trigger events are changes that open a window for improvement, such as a merger, new regulation, a new executive, a strategy change or an external assessment.
- What to understand
- Both build the case for action in phase 1. Pain points describe what hurts now; trigger events describe a change that makes action timely and sponsorship easier to obtain.
- How it shows up
- A scenario describes a situation, such as a new CIO joining after an acquisition, and asks whether it is a trigger event or a pain point.
- Common confusion
- Classifying a change in leadership or regulation as a pain point rather than a trigger event.
8.3 Creating the appropriate environmentSponsorship, ownership and conditions for success.
- What it means
- Before and during implementation, the enterprise needs an environment that supports change: direction and mandate from top management, clear ownership and accountability, stakeholder involvement, effective communication, and a program structure for governing the initiative.
- What to understand
- Success factors include visible sponsorship, tailoring to enterprise context, focusing on quick wins and the most beneficial improvements, and building on existing practices rather than starting from scratch.
- How it shows up
- A question asks what should be in place first for a governance program to succeed, and top management sponsorship is usually the answer.
- Common confusion
- Choosing a technical first step, such as buying a tool, over establishing sponsorship and mandate.
8.4 Implementation life cycleSeven phases framed as questions.
- What it means
- The life cycle has seven phases: 1 What are the drivers? 2 Where are we now? 3 Where do we want to be? 4 What needs to be done? 5 How do we get there? 6 Did we get there? 7 How do we keep the momentum going?
- What to understand
- Phases 2 and 3 assess current and target capability, phase 4 defines and plans improvement projects, phase 5 implements them, phase 6 checks whether benefits were achieved, and phase 7 sustains and restarts the cycle. It is iterative, not linear and final.
- How it shows up
- An activity is described and you choose the phase, such as defining improvement projects (phase 4) or monitoring whether benefits were realized (phase 6).
- Common confusion
- Swapping phase 4, which defines what needs to be done, with phase 5, which carries it out.
8.5 Programme management, change enablement and continual improvementThree perspectives that run through every phase.
- What it means
- Each phase is addressed from three perspectives: programme management (for example initiate programme, define road map, execute plan, realize benefits), change enablement (for example establish desire to change, form implementation team, embed new approaches, sustain) and the continual improvement life cycle (for example recognize need to act, assess current state, build and implement improvements, monitor and evaluate).
- What to understand
- Change enablement addresses behavioral and cultural aspects, programme management addresses planning, governance and benefits of the initiative, and continual improvement addresses the governance capability itself. Neglecting change enablement is a common reason improvements do not stick.
- How it shows up
- A scenario describes staff resistance to new governance practices and asks which perspective should address it, which is change enablement.
- Common confusion
- Answering a people or culture problem with a programme management action such as re-planning the schedule.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Seven life cycle phases
What are the drivers; where are we now; where do we want to be; what needs to be done; how do we get there; did we get there; how do we keep the momentum going.
- Remember
- Learn them in order as questions.
- Tested as
- Phase identification is the most common question type here.
- Trap
- Swapping phases 2 and 3 or 4 and 5.
-
Phase 2: Where are we now?
Assessing the current state, typically current capability levels of priority processes.
- Remember
- Measures the present.
- Tested as
- Assessment scenarios.
- Trap
- Calling it phase 3 because targets are discussed.
-
Phase 3: Where do we want to be?
Defining the target state and target capability levels, and the gap to close.
- Remember
- Defines the future.
- Tested as
- Target-setting scenarios.
- Trap
- Mixing it with the current-state assessment.
-
Phase 6: Did we get there?
Checking whether improvements delivered the expected benefits and targets.
- Remember
- Benefits realization and measurement.
- Tested as
- Post-implementation review scenarios.
- Trap
- Choosing phase 7 for a review of results.
-
Phase 7: How do we keep the momentum going?
Sustaining the new practices, reviewing overall success and starting the next cycle.
- Remember
- Implementation is continual.
- Tested as
- Sustainment questions.
- Trap
- Treating the program as finished after phase 6.
-
Pain points
Internal symptoms of weak governance, such as failed initiatives, repeated audit findings or significant incidents.
- Remember
- What hurts now.
- Tested as
- Classification questions.
- Trap
- Classifying a leadership change as a pain point.
-
Trigger events
Changes that create an opportunity for improvement, such as a merger, new regulation, new executive or new strategy.
- Remember
- What makes action timely.
- Tested as
- Classification questions.
- Trap
- Classifying repeated audit findings as a trigger event.
-
Change enablement
The perspective dealing with behavior and culture, from establishing desire to change to sustaining it.
- Remember
- People problems belong here.
- Tested as
- Resistance and adoption scenarios.
- Trap
- Answering resistance with a programme management action.
-
Programme management
The perspective that initiates and runs the program, defines the road map, executes the plan and realizes benefits.
- Remember
- Governs the initiative itself.
- Tested as
- Planning and benefits questions.
- Trap
- Using it for cultural resistance.
-
Continual improvement life cycle
The perspective that improves governance capability: recognize need, assess current state, define target, build, implement, operate and measure, monitor and evaluate.
- Remember
- Focuses on the governance system's capability.
- Tested as
- Perspective questions.
- Trap
- Confusing it with programme management.
-
Top management sponsorship
Direction and mandate from senior leadership for the governance program.
- Remember
- The first condition of a supportive environment.
- Tested as
- What-first questions.
- Trap
- Choosing tool selection as the first step.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Pain points vs. trigger events
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Pain points | Internal symptoms of weak governance, such as failed projects or repeated audit findings | Ongoing problems felt now | Labeling a merger or new regulation as a pain point |
| Trigger events | Changes such as a merger, new regulation or new executive | Events that make action timely | Labeling chronic cost overruns as a trigger event |
Programme management vs. change enablement vs. continual improvement
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Programme management | Initiates and runs the program, road map, plan and benefits | Governs the initiative | Using it to fix resistance |
| Change enablement | Establishes desire to change, forms the team, embeds and sustains new behavior | Addresses people and culture | Overlooking it when practices do not stick |
| Continual improvement life cycle | Assesses and improves governance capability | Addresses the governance system itself | Treating it as a one-off assessment |
Phase 2 vs. phase 3 vs. phase 6
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Phase 2: Where are we now? | Assess current state and capability | Measures the present before change | Confusing it with phase 6 measurement |
| Phase 3: Where do we want to be? | Define target state and gap | Sets the future | Confusing it with the current-state assessment |
| Phase 6: Did we get there? | Check whether improvements achieved targets and benefits | Measures after change | Choosing phase 7 for this review |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Target instead of current
- What candidates pick
- Phase 3 for rating current process capability.
- Why it looks right
- Targets are often discussed in the same workshop.
- Why it's wrong
- Measuring the present state answers where are we now, which is phase 2.
Clue to watch for Words such as current, as-is or baseline assessment.
-
Plan instead of execute
- What candidates pick
- Phase 4 for rolling out the new incident process.
- Why it looks right
- Phase 4 sounds like doing the work.
- Why it's wrong
- Phase 4 defines what needs to be done; implementing improvements is phase 5, how do we get there.
Clue to watch for The improvement is already defined and is now being deployed.
-
Programme fix for people problem
- What candidates pick
- Re-baselining the program schedule when staff ignore new practices.
- Why it looks right
- Delays look like a planning issue.
- Why it's wrong
- Resistance and failure to adopt are change enablement issues, needing communication, involvement and embedding.
Clue to watch for Staff resist, ignore or work around the new approach.
-
Leadership change as pain point
- What candidates pick
- Pain point for the arrival of a new CEO.
- Why it looks right
- Leadership change can feel disruptive.
- Why it's wrong
- A new executive is a trigger event that creates an opportunity for governance improvement.
Clue to watch for A discrete change such as a merger, new regulation or new executive.
-
Done after delivery
- What candidates pick
- Closing the program once improvements are implemented and measured.
- Why it looks right
- Projects usually end at delivery.
- Why it's wrong
- Phase 7 sustains the change and restarts the cycle, because governance improvement is continual.
Clue to watch for The question asks what happens after benefits are confirmed.
-
Tool first
- What candidates pick
- Selecting a governance tool as the first step of the program.
- Why it looks right
- Tools give quick visible progress.
- Why it's wrong
- The environment, especially top management direction and mandate, must be established first.
Clue to watch for The question asks what should happen FIRST.
Answer framework
For Implementation questions, place the activity by phase question, then by perspective.
- Decide whether the scenario is about why to start, classifying situations as pain points or trigger events, or about the environment, where sponsorship comes first.
- Match the activity to the phase question: drivers, current state, target state, what to do, doing it, checking results, or sustaining.
- Separate defining from doing: phase 4 defines improvement projects, phase 5 implements them.
- Assign the concern to a perspective: people and behavior to change enablement, plans and benefits to programme management, capability to continual improvement.
- Reject answers that close the program as soon as improvements are delivered, or that start with buying tools before sponsorship and mandate are in place.
Practice question
Want more like this? The COBIT 2019 Foundation practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the seven phases as questions and say them in order until they are automatic. For each phase, write one activity that clearly belongs to it, such as rating current capability for phase 2 or reviewing achieved benefits for phase 6. Most questions in this area are phase placement, so this list is the core of your preparation.
Next, learn the three perspectives and one keyword for each: programme management for plan and benefits, change enablement for people and behavior, continual improvement for governance capability. Then build two short lists of pain points and trigger events and practice classifying examples.
Candidates underestimate phase 7 and the environment conditions; remember that sponsorship comes first and that the cycle repeats. Afterwards, revisit Business Case and Performance Management, since the business case supports phase 1 and capability levels measure phases 2, 3 and 6, then take a full timed practice set across all eight topic areas.
FAQ
How much of the exam is Implementation?
ISACA weights it at 8%, roughly six of the 75 questions on a planning basis. ISACA does not publish per-area question counts.
What are the seven phases of the implementation life cycle?
What are the drivers; where are we now; where do we want to be; what needs to be done; how do we get there; did we get there; and how do we keep the momentum going.
What is the difference between a pain point and a trigger event?
A pain point is an internal symptom of weak governance, such as repeated audit findings. A trigger event is a change, such as a merger or a new regulation, that creates an opportunity to act.
What are the three perspectives in the life cycle?
Programme management, change enablement and the continual improvement life cycle. Each phase is addressed from all three.
Why is change enablement important?
Improvements often fail because people do not adopt them. Change enablement deals with behavior and culture, from establishing the desire to change to embedding and sustaining new practices.
Is implementation a one-time project?
No. Phase 7 sustains the changes and restarts the cycle, because governance improvement is continual.
How does this area connect to Designing a Tailored Governance System?
The Design Guide determines the tailored target governance system, which informs the drivers, current state and target state phases of the Implementation Guide.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 8 knowledge
You have covered pain points and trigger events, the supportive environment, the seven-phase life cycle and its three perspectives. Check whether you can place activities in the right phase under exam timing.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the COBIT 2019 Foundation AI tutor Get any concept explained your way