Category: Без рубрики

Let’s now look at the continual improvement model in ITIL 4.

The continual improvement model provides a structured approach for identifying and managing improvements.

It helps organisations understand where they are now, where they want to be, and how to get there.

The model consists of several steps that guide improvement activities.

These steps help ensure that improvements are planned, measured, and aligned with organisational objectives.

The continual improvement model can be applied to services, practices, and the organisation as a whole.

Using the model helps organisations make consistent and effective improvements.

Understanding the continual improvement model is important for applying continual improvement in practice.

---

2. How this applies to TakeCars (car-rental marketplace)

This section explains how TakeCars can turn “we should fix this” into a repeatable improvement discipline instead of reactive firefighting.

a) The continual improvement model = structured learning loop

In TakeCars terms, the model forces clarity:

• Where are we now?
  • High dispute rate on deposits
  • Slow supplier confirmations
• Where do we want to be?
  • Fewer disputes
  • Faster confirmations
• How do we get there?
  • Policy refinement
  • Automation
  • Supplier segmentation

Without this structure, improvements remain opinion-driven.

---

b) Preventing “random optimisation”

Marketplaces often:

• Fix what is loudest
• Optimise what feels urgent
• Chase symptoms instead of causes

The ITIL model forces:

• Baselines
• Targets
• Measurable outcomes

For TakeCars, this means:

• Measuring dispute resolution time before changing rules
• Tracking confirmation speed before automating
• Comparing cohorts before rolling out changes

---

c) Making improvement scalable

As TakeCars grows:

• Founders cannot decide every improvement
• Support cannot invent fixes ad hoc

The continual improvement model:

• Creates shared language
• Enables delegation
• Preserves consistency

This is how improvement survives growth.

---

3. Key ideas to read right before the exam (high-yield)

The continual improvement model is often tested as a “what is its purpose?” question.

Core understanding

The continual improvement model:

• Provides a structured approach
• Supports planning and managing improvements
• Helps move from current state to desired state

If an answer:

• Mentions structure and alignment → strong
• Mentions ad-hoc improvement → weak

---

Exam trap to avoid

Wrong answers often:

• Confuse the model with the guiding principles
• Treat it as a single step
• Limit it to IT only

Correct answers:

• Emphasise structured improvement
• Apply broadly
• Align with objectives

---

Fast exam shortcut

If the question asks:

• “How does ITIL structure improvement?”
  → Continual improvement model

---

One-line exam anchor

The continual improvement model provides a structured path from current state to desired state.

Keep this sentence in mind — it resolves most related exam questions instantly.

Let’s now take a closer look at the continual improvement component of the ITIL 4 service value system.

Continual improvement is a recurring organisational activity performed at all levels.

Its purpose is to ensure that services continually align with changing stakeholder needs and expectations.

Continual improvement applies to products, services, practices, and all elements of the service value system.

Improvement is not a one-time activity, but an ongoing effort.

Organisations should regularly assess their current state and identify opportunities for improvement.

Small, incremental improvements are often more effective than large, disruptive changes.

Continual improvement helps organisations remain competitive, relevant, and effective over time.

---

2. How this applies to TakeCars (car-rental marketplace)

This section explains how TakeCars stays relevant and trustworthy over time instead of relying on big redesigns.

a) Continual improvement is how marketplaces survive

For TakeCars:

• Customer expectations evolve
• Supplier behaviour adapts
• Regulations change
• Competitive benchmarks rise

ITIL’s message is clear:

Improvement is not a project — it is a habit.

Waiting for “the next big version” is how platforms stagnate.

---

b) What continual improvement looks like in TakeCars practice

Concrete, ITIL-aligned examples:

• Weekly review of dispute root causes
• Monthly refinement of deposit rules
• Incremental improvement of pickup instructions
• Progressive supplier scoring and feedback
• Iterative automation of support responses

None of these require a rewrite — they require discipline and cadence.

---

c) Improvement must be system-wide

ITIL explicitly says continual improvement applies to all SVS elements.

For TakeCars this means:

• Improving rules (governance)
• Improving flows (value streams)
• Improving behaviour (suppliers + customers)
• Improving tools (platform)
• Improving decisions (support judgment)

Improving only features while ignoring behaviour or policy creates imbalance.

---

3. Key ideas to read right before the exam (high-yield)

Continual improvement is a core ITIL 4 concept and often tested in principle-based questions.

Core understanding

Continual improvement:

• Is ongoing
• Applies at all levels
• Applies to all components
• Responds to changing needs

If an answer:

• Treats improvement as one-off → wrong
• Emphasises continuous alignment → strong

---

Exam trap to avoid

Wrong answers often:

• Frame improvement as a project
• Limit improvement to IT tools
• Assume large changes are better

Correct answers:

• Emphasise regular review
• Support incremental change
• Apply improvement broadly

---

Fast exam shortcut

If a question asks:

• “How does ITIL ensure relevance over time?”
  → Continual improvement

---

One-line exam anchor

Improvement is continuous and applies everywhere.

Keep this sentence in mind — it resolves most continual improvement questions instantly.

---

Let’s now take a closer look at the service value chain within the ITIL 4 service value system.

The service value chain is an operating model that outlines the key activities required to respond to demand and facilitate value creation.

It provides a flexible set of activities that can be combined in different ways to create value.

The service value chain includes six activities: plan, improve, engage, design and transition, obtain or build, and deliver and support.

These activities are not linear and do not have to be followed in a specific order.

Different value streams can use different combinations of these activities depending on the scenario.

The service value chain helps organisations understand how work flows across the organisation to create value.

Understanding the service value chain is essential for applying ITIL in practice.

---

2. How this applies to TakeCars (car-rental marketplace)

This section explains how TakeCars should think about work as flow, not as departments or features.

a) TakeCars work is demand-driven, not function-driven

In ITIL terms, TakeCars demand comes from:

• A customer wanting mobility
• A supplier wanting bookings
• A problem that needs resolution

The service value chain shows that:

• Work should flow in response to demand
• Activities are combined dynamically, not rigidly

This matches how TakeCars actually operates in real life.

---

b) Mapping TakeCars scenarios to the service value chain

Example: Standard booking

• Engage → Deliver & Support → Improve

Example: New supplier onboarding

• Plan → Design & Transition → Obtain/Build → Engage

Example: Incident during rental

• Engage → Deliver & Support → Improve

The key insight:

You do not “run the chain” — you select activities based on the situation.

---

c) Why non-linearity matters for TakeCars

Many operational problems come from assuming:

• Every case must follow the same path
• Every customer needs the same steps
• Every supplier interaction is identical

ITIL explicitly rejects this.

This legitimises:

• Short paths for simple cases
• Deep paths for complex cases
• Skipping unnecessary steps

This is how TakeCars scales without drowning in process.

---

3. Key ideas to read right before the exam (high-yield)

The service value chain is a core ITIL 4 Foundation topic.

Core understanding

The service value chain:

• Is an operating model
• Responds to demand
• Facilitates value creation
• Is flexible and non-linear

If an answer:

• Treats it as rigid or sequential → wrong

---

Six activities (must be exact)

• Plan
• Improve
• Engage
• Design and Transition
• Obtain or Build
• Deliver and Support

Any missing or altered wording is a red flag.

---

Exam trap to avoid

Wrong answers often:

• Confuse the service value chain with a process
• Assume all activities are always used
• Enforce a fixed order

Correct answers:

• Emphasise flexibility
• Combine activities as needed
• Focus on value creation

---

Fast exam shortcut

If the question asks:

• “How does ITIL respond to demand?”
  → Service value chain

---

One-line exam anchor

The service value chain is a flexible operating model for value creation.

Keep this sentence in mind — it resolves most service value chain questions quickly.

The next guiding principle of ITIL 4 is keep it simple and practical.

This principle encourages organisations to use the minimum number of steps, processes, and controls necessary to achieve objectives.

Unnecessary complexity can reduce efficiency and create confusion.

Processes and practices should be designed to be easy to understand and use.

If a process or activity does not add value, it should be eliminated or simplified.

Keeping things simple helps organisations respond more quickly to change.

This principle supports efficiency, clarity, and effectiveness in service management.

---

2. How this applies to TakeCars (car-rental marketplace)

This principle explains why complexity quietly kills marketplaces.

a) Complexity creates friction and cost

For TakeCars, unnecessary complexity shows up as:

• Overly detailed policies customers don’t read
• Multi-step booking confirmations
• Too many supplier exceptions
• Support scripts that require escalation

ITIL is explicit:

If it doesn’t add value, remove or simplify it.

---

b) Simplicity increases trust

From a customer’s perspective:

• Simple pickup instructions = confidence
• Simple pricing = fewer disputes
• Simple damage rules = less fear

From a supplier’s perspective:

• Simple onboarding = faster activation
• Simple rules = better compliance

Simplicity is not “cutting corners” — it is value protection.

---

c) Practical beats theoretically correct

ITIL deliberately says practical, not perfect.

For TakeCars this means:

• A “good enough” automated rule is better than a perfect manual one
• A clear default beats a complex exception matrix
• A fast resolution beats a technically flawless argument

This principle legitimises pragmatic decisions over internal purity.

---

3. Key ideas to read right before the exam (high-yield)

This guiding principle appears in process design and improvement scenarios.

Core understanding

“Keep it simple and practical” means:

• Minimise steps and controls
• Remove unnecessary complexity
• Focus on usability and value

If an answer:

• Simplifies processes → strong
• Reduces unnecessary work → strong

---

Exam trap to avoid

Wrong answers often:

• Add controls “just in case”
• Increase documentation without value
• Assume complexity equals maturity

Correct answers:

• Simplify workflows
• Remove non-value steps
• Improve clarity

---

Fast exam shortcut

If a scenario mentions:

• Confusion
• Delays
• Overhead

The correct answer usually involves:

“Simplifying and making the process more practical.”

---

One-line exam anchor

Simplicity improves efficiency and value.

Keep this sentence in mind during the exam.

---

Let’s now take a closer look at governance within the ITIL 4 service value system.

Governance is the means by which an organisation is directed and controlled.

It ensures that organisational objectives are achieved and that risks are managed appropriately.

Governance provides oversight and accountability for decision-making.

In ITIL, governance is responsible for evaluating, directing, and monitoring organisational activities.

This helps ensure that services remain aligned with stakeholder needs and organisational strategy.

Effective governance supports transparency, compliance, and continual improvement.

Governance plays a critical role in ensuring that value is created in a controlled and sustainable way.

---

2. How this applies to TakeCars (car-rental marketplace)

This section explains why TakeCars cannot rely on “good intentions” or ad-hoc decisions at scale.

a) Governance is not bureaucracy — it is decision authority

For TakeCars, governance answers:

• Who decides refunds beyond policy?
• Who can override supplier penalties?
• Who changes deposit rules?
• Who accepts regulatory risk?

Without clear governance:

• Support improvises
• Product pushes changes blindly
• Suppliers exploit inconsistencies
• Trust erodes

Governance is about clear accountability, not control for its own sake.

---

b) Evaluating, directing, monitoring — applied to TakeCars

Mapped directly from ITIL:

• Evaluate
  • Are current rules still aligned with customer trust?
  • Are suppliers meeting expectations?
• Direct
  • Set policies on deposits, cancellations, insurance
  • Define acceptable risk levels
• Monitor
  • Dispute rates
  • Refund timelines
  • Supplier performance
  • Legal exposure

This loop prevents drift and reactionary decision-making.

---

c) Governance protects long-term value

ITIL explicitly links governance to sustainability.

For TakeCars:

• Saying “yes” to every customer destroys supplier trust
• Saying “no” to every customer destroys brand trust
• Governance defines the balance point

This allows TakeCars to scale without becoming arbitrary or unfair.

---

3. Key ideas to read right before the exam (high-yield)

Governance is a frequent conceptual exam topic, often tested indirectly.

Core understanding

Governance:

• Directs and controls the organisation
• Ensures objectives are met
• Manages risk
• Provides oversight and accountability

If an answer:

• Mentions evaluate, direct, monitor → very strong

---

Exam trap to avoid

Wrong answers often:

• Treat governance as day-to-day operations
• Confuse governance with management
• Ignore accountability

Correct answers:

• Emphasise oversight
• Link to strategy and risk
• Separate governance from execution

---

Fast exam shortcut

If a question asks:

• “Who ensures alignment with strategy?”
• “Who oversees risk and compliance?”

The answer usually involves:

Governance

---

One-line exam anchor

Governance ensures the organisation does the right things in the right way.

Keep this sentence in mind — it resolves most governance questions.

---

Ready for the next file

Upload the next SRT when ready.
We will continue with the same three-layer structure:

1. Exact transcript
2. TakeCars application lens
3. Exam-day compression notes

You are now moving into the control and oversight layer of ITIL 4 — an area where exam questions reward clarity about who decides versus who does.

Now let’s take a closer look at the service value system in ITIL 4.

The service value system describes how all the components and activities of an organisation work together to facilitate value creation.

It provides a holistic view of how value is co-created through services.

The service value system ensures that an organisation’s activities remain aligned with its objectives and stakeholder needs.

It includes guiding principles, governance, the service value chain, practices, and continual improvement.

All of these components interact to support the creation of value.

The service value system helps organisations respond to demand and opportunities in a consistent and coordinated way.

Understanding the service value system is essential for understanding how ITIL 4 fits together as a whole.

---

2. How this applies to TakeCars (car-rental marketplace)

This section explains how TakeCars should be understood as a single, coherent value system — not a collection of tools, rules, or teams.

a) TakeCars already has a Service Value System (even if unnamed)

Mapped directly:

• Guiding principles
  • Trust first
  • Customer outcome over internal convenience
  • Simplicity beats perfection
• Governance
  • Risk rules (deposits, insurance)
  • Supplier eligibility
  • Escalation authority
• Service value chain
  • Plan → Engage → Deliver & Support → Improve (with others as needed)
• Practices
  • Supplier management
  • Incident handling
  • Payment handling
  • Customer support
• Continual improvement
  • Reviews
  • Dispute analysis
  • Flow refinements

ITIL simply gives names to what TakeCars already does implicitly.

---

b) Why fragmentation hurts TakeCars

Without a conscious SVS view:

• Policies drift away from value
• Automation breaks trust
• Support fights product decisions
• Growth creates chaos

The SVS lens forces one key question:

“Does this change improve the system’s ability to co-create value?”

That question prevents local optimisation disasters.

---

c) The SVS explains why “quick fixes” fail

ITIL shows that:

• Changing tools without governance fails
• Changing policies without practices fails
• Changing workflows without principles fails

For TakeCars:

• New features without support alignment fail
• New rules without supplier buy-in fail
• New automation without optimisation fails

SVS thinking prevents isolated fixes.

---

3. Key ideas to read right before the exam (high-yield)

The Service Value System is a core structural concept in ITIL 4 Foundation.

Core definition (recognise instantly)

The service value system describes how all components and activities of an organisation work together to facilitate value creation.

Key words:

• All components
• Work together
• Facilitate value creation

---

SVS components (must list correctly)

The SVS includes:

• Guiding principles
• Governance
• Service value chain
• Practices
• Continual improvement

If an answer:

• Misses one → wrong
• Adds something else → wrong

---

Exam trap to avoid

Wrong answers often:

• Treat SVS as a process
• Confuse it with the service value chain
• Focus only on operations

Correct answers:

• Emphasise integration
• Highlight alignment with objectives
• Show holistic coordination

---

Fast exam shortcut

If the question asks:

• “How does ITIL ensure everything works together?”
  → Service Value System

---

One-line exam anchor

The SVS is the big picture of value creation in ITIL 4.

Keep this sentence in your head — it resolves most SVS questions instantly.

---

The final guiding principle of ITIL 4 is optimize and automate.

This principle encourages organisations to maximise the value of work done by humans and machines.

Before automating, organisations should ensure that processes are effective and efficient.

Automating inefficient processes can increase waste and complexity.

Optimisation should focus on improving performance, reducing errors, and increasing consistency.

Automation should be applied where it adds value and supports organisational objectives.

This principle recognises that automation can improve speed and reliability when used appropriately.

Optimise and automate supports continual improvement and better service outcomes.

---

2. How this applies to TakeCars (car-rental marketplace)

This principle lands directly in TakeCars’ core competence and explains how automation should (and should not) be used.

a) Automate only after fixing the process

ITIL is explicit:

Automating a bad process makes the bad outcome happen faster.

For TakeCars:

• Automating supplier confirmations without fixing reliability → faster failures
• Automating deposits without clear damage rules → faster disputes
• Automating refunds without safeguards → cashflow risk

Optimise first. Automate second.

---

b) Where automation does add real value for TakeCars

High-value automation areas include:

• Booking confirmations and reminders
• Pickup instructions and location sharing
• Supplier response time tracking
• Deposit release triggers
• Post-rental review requests

These reduce:

• Manual work
• Errors
• Response time
• Support load

---

c) Human judgement still matters

ITIL explicitly values human decision-making.

For TakeCars:

• Edge-case disputes
• Goodwill refunds
• Supplier discipline
• Crisis handling

Automation should support, not replace, judgment.

The best marketplaces automate the routine and elevate humans to exceptions.

---

3. Key ideas to read right before the exam (high-yield)

This guiding principle appears in process improvement and technology scenarios.

Core understanding

“Optimize and automate” means:

• Improve processes first
• Automate only where it adds value
• Balance human and machine work

If an answer:

• Automates blindly → wrong
• Optimises before automating → strong

---

Exam trap to avoid

Wrong answers often:

• Suggest automating everything
• Ignore process effectiveness
• Treat automation as a goal

Correct answers:

• Emphasise optimisation first
• Apply automation selectively
• Focus on value and outcomes

---

Fast exam shortcut

If a scenario mentions:

• New tools
• Automation
• Efficiency

The correct answer usually includes:

“Optimise the process before automating it.”

---

One-line exam anchor

Don’t automate waste.

Repeat this sentence mentally — it resolves most automation questions.

---

Guiding Principles — COMPLETE

You have now covered all 7 ITIL 4 guiding principles:

1. Focus on value
2. Start where you are
3. Progress iteratively with feedback
4. Collaborate and promote visibility
5. Think and work holistically
6. Keep it simple and practical
7. Optimize and automate

This is one of the highest-yield sections of the ITIL 4 Foundation exam, and you now understand it not just academically, but operationally through TakeCars.

If you want next, we can:

• Build a one-page TakeCars × ITIL guiding principles map
• Create a 10-minute exam cram sheet
• Continue with the next video segment

Just upload the next file or tell me how you’d like to proceed.

The next guiding principle of ITIL 4 is think and work holistically.

This principle encourages organisations to consider the whole system rather than focusing on individual parts.

Services are complex and involve many components, teams, and stakeholders.

Optimising one part of the system in isolation can create problems elsewhere.

Thinking holistically helps organisations understand how different elements interact and depend on each other.

This principle supports better decision-making and more sustainable improvements.

By considering the entire service, organisations can avoid unintended consequences and improve overall performance.

---

2. How this applies to TakeCars (car-rental marketplace)

This principle explains why local optimisations often backfire in marketplaces.

a) Local optimisation breaks global value

For TakeCars, common mistakes include:

• Optimising supplier payouts → suppliers happy, customers angry
• Optimising refund resistance → short-term cash, long-term trust loss
• Optimising conversion → support overload later

ITIL’s warning is clear:

Improving one part in isolation can damage the whole system.

---

b) TakeCars is a system, not a set of features

A holistic TakeCars view includes:

• Customer expectations
• Supplier behaviour
• Support capacity
• Legal exposure
• Brand trust
• Cash flow timing

Changing any one element (e.g. deposits, cancellation rules) affects all others.

Good decisions consider second- and third-order effects.

---

c) Holistic thinking improves strategy, not just ops

Applied well, this principle helps TakeCars:

• Avoid feature-driven roadmaps
• Design policies that scale
• Balance growth, risk, and trust
• Prevent “fix one thing, break two” cycles

This is leadership-level thinking, not just operational hygiene.

---

3. Key ideas to read right before the exam (high-yield)

This guiding principle appears in system-design and optimisation scenarios.

Core understanding

“Think and work holistically” means:

• Consider the entire service
• Understand interdependencies
• Avoid siloed optimisation

If an answer:

• Optimises one area without considering impact → weak
• Considers system-wide effects → strong

---

Exam trap to avoid

Wrong answers often:

• Focus on one team or process
• Ignore downstream effects
• Treat services as linear and simple

Correct answers:

• Consider multiple components
• Acknowledge dependencies
• Aim for overall value

---

Fast exam shortcut

If a scenario mentions:

• Conflicting improvements
• Unexpected side effects
• Siloed teams

The correct answer usually involves:

“Taking a holistic view of the service.”

---

One-line exam anchor

Optimising parts does not guarantee optimising the whole.

Keep this sentence in your head when answering system-level questions.

---

Ready for the next file

Upload the next SRT when ready.
We will continue with the same three-layer structure:

1. Exact transcript
2. TakeCars application lens
3. Exam-day compression notes

You are now covering the systems-thinking core of ITIL — an area where exam questions reward maturity of understanding rather than memorisation.

The next guiding principle of ITIL 4 is collaborate and promote visibility.

This principle highlights the importance of working together across teams and stakeholders.

Collaboration helps organisations break down silos and improve communication.

Promoting visibility means making work, progress, and information visible to everyone involved.

When people can see what is happening, they can make better decisions and identify issues earlier.

Transparency builds trust and supports more effective collaboration.

This principle applies both within the organisation and with external partners and stakeholders.

By collaborating and promoting visibility, organisations can improve outcomes and reduce misunderstandings.

---

2. How this applies to TakeCars (car-rental marketplace)

This principle directly addresses one of the hardest marketplace problems: hidden information.

a) Marketplaces fail in the dark

For TakeCars, lack of visibility causes:

• Customer anxiety (“Is the car confirmed?”)
• Supplier frustration (“What did the customer agree to?”)
• Support overload (“What actually happened?”)

ITIL’s answer is explicit: make work and status visible.

---

b) Collaboration across all three sides

“Collaborate” here is not just internal.

For TakeCars it means:

• Customer ↔ TakeCars ↔ Supplier
• Shared understanding of:
  • Pickup time
  • Location
  • Insurance terms
  • Deposit rules
  • Damage responsibility

Every hidden assumption becomes a future dispute.

---

c) Visibility is a trust accelerator

Concrete TakeCars examples:

• Clear booking status (“requested / confirmed / ready”)
• Visible supplier response times
• Explicit inclusions/exclusions in listings
• Transparent refund timelines

Visibility reduces:

• Support tickets
• Defensive behaviour
• Blame-shifting

This principle directly lowers cost and increases trust.

---

3. Key ideas to read right before the exam (high-yield)

This guiding principle appears often in communication and coordination scenarios.

Core understanding

“Collaborate and promote visibility” means:

• Work together across boundaries
• Share information openly
• Make progress and issues visible

If an answer:

• Breaks silos → strong
• Improves transparency → strong

---

Exam trap to avoid

Wrong answers often:

• Emphasise individual work
• Hide information “for efficiency”
• Treat visibility as optional

Correct answers:

• Promote shared understanding
• Increase transparency
• Support early issue detection

---

Fast exam shortcut

If a scenario mentions:

• Miscommunication
• Delays
• Surprises

The correct answer usually involves:

“Improving collaboration and visibility.”

---

One-line exam anchor

Visibility enables better decisions and trust.

Keep this sentence in mind when choosing answers under time pressure.

---

The next guiding principle of ITIL 4 is progress iteratively with feedback.

This principle emphasises the importance of breaking work into smaller, manageable pieces.

Rather than attempting large changes all at once, organisations should make incremental improvements.

Each improvement should be evaluated, and feedback should be used to guide the next steps.

Progressing iteratively helps reduce risk and allows organisations to learn and adapt.

Feedback can come from customers, users, partners, and internal stakeholders.

Using feedback ensures that improvements are aligned with real needs and expectations.

This principle supports continuous learning and continual improvement.

---

2. How this applies to TakeCars (car-rental marketplace)

This principle describes how TakeCars should safely evolve without breaking trust or operations.

a) Iteration protects marketplace trust

For TakeCars:

• Large, sudden changes break supplier behaviour
• Big redesigns confuse repeat customers
• Policy overhauls create unintended loopholes

ITIL explicitly recommends:

Small changes, validated by feedback.

This is how you avoid marketplace shock.

---

b) Feedback sources TakeCars should prioritise

ITIL treats feedback as multi-source, not just “user opinions”.

For TakeCars, high-quality feedback includes:

• Post-rental reviews
• Support tickets (especially repeats)
• Refund and dispute patterns
• Supplier response times
• Drop-offs in booking flow

These are signals, not noise.

---

c) Iteration beats opinions

This principle legitimises a powerful rule:

• Test before scaling
• Observe before enforcing
• Learn before locking policy

For example:

• Trial a new deposit rule with one supplier cohort
• Pilot faster payouts in one region
• Test simplified handover instructions on airport rentals

Each iteration reduces risk while increasing learning.

---

3. Key ideas to read right before the exam (high-yield)

This guiding principle is a scenario-question favourite.

Core understanding

“Progress iteratively with feedback” means:

• Break work into smaller steps
• Gather feedback continuously
• Adjust based on learning

If an answer:

• Promotes big, one-time changes → weak
• Emphasises learning and feedback → strong

---

Exam trap to avoid

Wrong answers often:

• Suggest full redesigns
• Ignore stakeholder feedback
• Assume perfect upfront knowledge

Correct answers:

• Emphasise iteration
• Use feedback
• Reduce risk

---

Fast exam shortcut

If a scenario mentions:

• Uncertainty
• Risk
• Change

The correct answer usually includes:

“Make small improvements and gather feedback.”

---

One-line exam anchor

Improve in small steps, guided by feedback.

Keep this sentence in your head during the exam.

---