---

Software development and management is the practice of designing, developing, releasing, and maintaining software products and services.

Its purpose is to ensure that software supports organisational objectives and delivers value to users.

This practice includes activities such as coding, testing, deployment, and maintenance.

Software development and management should be integrated with other service management practices.

It supports continual improvement and the reliable delivery of services.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains how TakeCars’ product evolves continuously without destabilising live operations.

a) Software development at TakeCars is a service enabler, not the service itself

For TakeCars, software enables:

• Booking and pricing logic
• Payments and refunds
• Host and customer communication
• Support workflows
• Automation and monitoring

If software development is disconnected from service management, features ship but value does not.

---

b) End-to-end responsibility: build, release, maintain

ITIL explicitly includes maintenance, not just development.

At TakeCars this means:

• Fixing edge cases discovered in production
• Refactoring fragile logic
• Retiring unused features
• Maintaining integrations with suppliers

Unmaintained software becomes operational risk.

---

c) Integration with other practices (exam-relevant)

Software development and management must integrate with:

• Change enablement (approval and risk control)
• Release management (making changes usable)
• Deployment management (putting changes live)
• Service validation and testing (fit for purpose/use)
• Incident and problem management (learning from failures)

The exam often tests this integration mindset.

---

d) Continual improvement through software

Many improvements at TakeCars are software-driven:

• Reducing manual steps
• Preventing known errors
• Improving visibility and metrics
• Enforcing consistent rules

But improvement only happens when software changes are aligned with real service pain points.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of software development and management?”

Correct logic:

• Design, build, release, and maintain software
• Support organisational objectives
• Deliver value through reliable services

Answers focusing only on coding or development tools are incomplete.

---

3. Key Things to Read / Remember Right Before the Exam

Software development and management (moderate–high probability)

• A technical management practice
• Covers design, development, release, and maintenance
• Supports service delivery and value creation
• Integrated with other practices

---

Common exam traps

• Software development is separate from service management → False
• Development ends at release → False
• Software management is only about tools → False

---

One-line memory hook

Software development and management ensures software continuously supports reliable, valuable services.

---

---

Infrastructure and platform management is the practice of overseeing the infrastructure and platforms used to deliver services.

Its purpose is to ensure that infrastructure and platforms are reliable, available, and meet current and future service needs.

This practice includes managing compute, storage, networks, and cloud services.

Infrastructure and platform management supports service performance, scalability, and resilience.

It works closely with other practices to enable effective service delivery.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains the foundation that keeps TakeCars running reliably, even though customers rarely see it directly.

a) What “infrastructure and platform” means at TakeCars

It includes:

• Cloud hosting and databases
• Booking and payment platforms
• Messaging and notification services
• Monitoring and logging tools
• Backup and recovery systems

If these fail, no amount of good support can save the experience.

---

b) Reliability, availability, scalability

Reliability

• Bookings are processed correctly
• Payments are not duplicated or lost
• Data is consistent

Failure example:

• Booking confirmed but not saved correctly

---

Availability

• Platform accessible during peak travel times
• Support tools usable during incidents

Failure example:

• Platform outage during airport pickup windows

---

Scalability

• Handles seasonal demand spikes
• Absorbs marketing-driven traffic surges

Failure example:

• Slowdowns during holiday bookings

---

c) Resilience and future needs

ITIL stresses current and future needs.

For TakeCars:

• New cities
• More hosts
• More integrations
• Higher transaction volume

Infrastructure must grow without becoming fragile.

---

d) Relationship with other practices

Infrastructure and platform management enables:

• Monitoring and event management
• Service continuity management
• Information security management
• Incident and problem management

It does not operate in isolation.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of infrastructure and platform management?”

Correct logic:

• Ensure reliable, available infrastructure
• Support current and future service needs
• Enable effective service delivery

Answers focusing only on hardware are incomplete.

---

3. Key Things to Read / Remember Right Before the Exam

Infrastructure and platform management (moderate–high probability)

• A technical management practice
• Manages infrastructure and platforms
• Ensures reliability, availability, scalability
• Supports service delivery and resilience

---

Common exam traps

• Infrastructure management is only about servers → False
• Infrastructure management is separate from service quality → False
• Infrastructure management ignores future needs → False

---

One-line memory hook

Infrastructure and platform management keeps the technical foundation reliable and ready for growth.

---

---

Service desk is the practice of capturing demand for incident resolution and service requests.

The service desk acts as the single point of contact between the service provider and its users.

Its purpose is to provide a clear channel for communication and to coordinate support activities.

The service desk helps ensure that incidents and service requests are logged, tracked, and resolved efficiently.

It supports user communication throughout the service lifecycle.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice describes the operational front door of TakeCars, where customer experience is won or lost.

a) Service desk = single point of contact at TakeCars

At TakeCars, the service desk is:

• Customer support chat or email
• Emergency contact during trips
• Host support channel
• Dispute intake point

Even if spread across tools, it must behave as one coherent interface.

---

b) Capturing demand correctly matters

The service desk captures:

• Incidents
  • No car at pickup
  • Breakdown during trip
• Service requests
  • Change booking
  • Add extras
  • Request invoice

If demand is misclassified:

• Incidents are delayed
• Requests clog urgent queues

Service desk triage quality directly affects outcomes.

---

c) Coordination, not just communication

The service desk does not “fix everything” itself.

It coordinates:

• Hosts
• Operations
• Payments
• Insurance
• Engineering (when needed)

A weak service desk causes:

• Duplicate work
• Lost context
• Inconsistent decisions

---

d) User communication throughout the lifecycle

ITIL explicitly includes:

• Keeping users informed
• Setting expectations
• Providing updates

For TakeCars:

• Clear status during incidents
• Predictable response timelines
• Transparent resolution steps

Silence destroys trust faster than bad news.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of the service desk?”

Correct logic:

• Single point of contact
• Capture incidents and service requests
• Coordinate support
• Communicate with users

Answers describing the service desk as only a technical support function are incorrect.

---

3. Key Things to Read / Remember Right Before the Exam

Service desk (very high probability)

• A service management practice
• Single point of contact
• Captures incidents and service requests
• Coordinates and communicates

---

Common exam traps

• Service desk resolves all issues directly → False
• Service desk is optional → False
• Service desk is only for IT issues → False

---

One-line memory hook

The service desk is the single point of contact that coordinates support and communication.

---

---

Service validation and testing is the practice of ensuring that new or changed services meet defined requirements and expectations.

Its purpose is to ensure that services deliver the intended value and quality before they are released or deployed.

Service validation and testing verifies that services are fit for purpose and fit for use.

Testing should be planned early and performed throughout the service lifecycle.

Effective validation and testing reduce the risk of service failure.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains how TakeCars prevents failures before customers experience them, especially during change.

a) What “validation and testing” means at TakeCars

It is not only technical testing. It includes:

• Booking flow testing
• Pricing and fee calculation checks
• Policy logic verification
• Host onboarding scenarios
• Support workflow simulations

Anything that affects customer outcomes must be validated.

---

b) Fit for purpose vs fit for use (exam-critical)

• Fit for purpose (utility)
  • Does the change support the intended outcome?
  • Example: Can a customer actually complete a booking?
• Fit for use (warranty)
  • Is it reliable under real conditions?
  • Example: Does it work during peak demand without errors?

A feature can pass one and fail the other.

---

c) Testing throughout the lifecycle

ITIL explicitly says testing should start early.

At TakeCars:

• Test rules before rollout
• Test edge cases (late pickup, extensions)
• Test failure paths (payment retry, host cancellation)

Late testing leads to live incidents.

---

d) Risk reduction through validation

Good validation and testing:

• Reduce incidents after release
• Protect active bookings
• Reduce support load
• Increase confidence in change

Skipping validation transfers risk directly to customers.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of service validation and testing?”

Correct logic:

• Ensure services meet requirements
• Ensure fit for purpose and fit for use
• Reduce risk of failure

Answers focusing only on defect detection or development are incomplete.

---

3. Key Things to Read / Remember Right Before the Exam

Service validation and testing (high probability)

• A service management practice
• Ensures services meet requirements
• Confirms fit for purpose and fit for use
• Reduces risk before release or deployment

---

Common exam traps

• Testing happens only after deployment → False
• Testing focuses only on technology → False
• Validation guarantees zero failure → False

---

One-line memory hook

Service validation and testing confirm that services are ready and reliable before going live.

---

---

Deployment management is the practice of moving new or changed service components into live environments.

Its purpose is to ensure that deployments are carried out in a controlled and effective manner.

Deployment management may involve deploying software, hardware, documentation, or other service components.

Deployments should be planned and coordinated to minimise disruption to services.

Deployment management works closely with release management and change enablement.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains how changes are physically or logically put into production, as distinct from approval and release communication.

a) What a “deployment” is at TakeCars

Deployments include:

• Pushing new code to production
• Enabling new pricing logic
• Activating new host rules
• Updating production configuration
• Publishing new operational documentation

A deployment is the act of putting components live.

---

b) Deployment vs release vs change (exam-critical clarity)

• Change enablement
  • Decides if/when a change is allowed
• Release management
  • Packages and prepares changes for use
• Deployment management
  • Moves components into the live environment

These are related but not the same.

---

c) Controlled deployments in TakeCars

Why control matters:

• Live bookings are always in progress
• Errors affect real trips immediately

Good deployment practices include:

• Deploying outside peak pickup times
• Feature toggles for gradual rollout
• Rollback capability
• Coordination with support

Poor deployments become incidents.

---

d) Minimising disruption

ITIL stresses minimising disruption, not eliminating change.

For TakeCars:

• Small, frequent deployments are safer than big ones
• Visibility to operations reduces surprises
• Coordination reduces support spikes

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of deployment management?”

Correct logic:

• Move new or changed components into live use
• Do so in a controlled way
• Minimise service disruption

Answers suggesting deployment management approves changes or designs releases are incorrect.

---

3. Key Things to Read / Remember Right Before the Exam

Deployment management (high probability)

• A service management practice
• Deploys components into live environments
• Minimises disruption
• Works with change enablement and release management

---

Common exam traps

• Deployment management decides what to change → False
• Deployment management is the same as release management → False
• Deployments should be unplanned → False

---

One-line memory hook

Deployment management carefully moves changes into live use without disrupting services.

---

Release management is the practice of making new and changed services and features available for use.

Its purpose is to ensure that releases are delivered successfully and meet stakeholder expectations.

Release management supports the transition of services into live environments.

Releases should be planned, scheduled, and communicated clearly.

Release management works closely with change enablement and deployment activities.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

Release management explains how changes actually reach users safely, which is critical in a live marketplace with active bookings.

a) What a “release” is at TakeCars

Releases include:

• New platform features
• Pricing or fee changes
• Policy updates exposed in the UI
• Host onboarding changes
• Support workflow changes
• Bug fixes that affect booking flow

A release is not the same as a change; it is the delivery of that change into use.

---

b) Purpose: successful, predictable delivery

Key ITIL point:

• Release management focuses on making changes usable
• Not just building them

For TakeCars:

• A feature is useless if hosts misunderstand it
• A policy change fails if customers are surprised
• A bug fix fails if it breaks active bookings

---

c) Planning, scheduling, and communication

Effective release management at TakeCars includes:

• Releasing low-risk changes outside peak booking times
• Clear communication to hosts and support
• Updated help content or internal guidance
• Rollback plans if something goes wrong

Unplanned releases create incidents.

---

d) Relationship with change enablement

• Change enablement
  • Decides whether and when a change is approved
• Release management
  • Packages and delivers the change into use

The exam often tests this distinction.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of release management?”

Correct logic:

• Make new and changed services available for use
• Ensure releases meet expectations
• Support smooth transition into live use

Answers focusing only on development or testing are incomplete.

---

3. Key Things to Read / Remember Right Before the Exam

Release management (high probability)

• A service management practice
• Delivers changes into use
• Focuses on successful releases
• Involves planning, scheduling, communication

---

Common exam traps

• Release management approves changes → False
• Release management is the same as deployment → False
• Releases can be unplanned → False

---

One-line memory hook

Release management makes approved changes usable without disrupting services.

---

---

Monitoring and event management is the practice of systematically observing services and service components, and recording and reporting selected changes of state identified as events.

An event is any change of state that has significance for the management of a service or service component.

The purpose of monitoring and event management is to identify and manage events that could affect service performance.

Monitoring helps detect issues early and supports proactive management.

Not all events require action, but some may trigger alerts or responses.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains how TakeCars detects problems before customers feel them, which is a major differentiator at scale.

a) What “monitoring” means at TakeCars

Monitoring is not limited to servers. It includes:

• Booking confirmation delays
• Host response time spikes
• Cancellation rate anomalies
• Payment failures
• Support backlog growth
• Platform availability

Anything that signals a potential service issue can and should be monitored.

---

b) Events vs incidents (exam-critical distinction)

• Event
  • A detectable change of state
  • May or may not require action

Examples:

• Host response time exceeds threshold
• Payment retry rate increases
• Booking confirmations slow down
• Incident
  • Service interruption or quality reduction

Events may trigger incidents, but are not incidents themselves.

---

c) Proactive value for TakeCars

Effective monitoring allows:

• Early intervention before pickups fail
• Throttling risky hosts
• Adding support capacity before queues explode
• Switching providers before full outage

This protects outcomes and warranty.

---

d) Not all events need action

ITIL explicitly states:

• Some events are informational
• Some are warnings
• Some require immediate response

For TakeCars:

• Informational: daily booking volume
• Warning: cancellation rate trending up
• Exception: payment provider outage

Clear thresholds prevent alert fatigue.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of monitoring and event management?”

Correct logic:

• Observe services and components
• Detect and manage significant events
• Support proactive management
• Prevent incidents where possible

Answers implying all events require action are incorrect.

---

3. Key Things to Read / Remember Right Before the Exam

Monitoring and event management (high probability)

• A service management practice
• Observes services and components
• Detects events
• Supports proactive response

---

Event definition (frequently tested)

• Any change of state
• Significant for service management
• May or may not require action

---

Common exam traps

• All events are incidents → False
• All events require action → False
• Monitoring is only technical → False

---

One-line memory hook

Monitoring detects events early so incidents can be prevented or managed proactively.

---

---

Service continuity management is the practice of ensuring that services can continue to be delivered at acceptable levels in the event of a disruption.

Its purpose is to reduce the risk of service disruption and to ensure service recovery if disruption occurs.

Service continuity management includes planning for major incidents and disasters.

It ensures that recovery plans are in place and tested.

Service continuity management supports organisational resilience and reliability.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains how TakeCars survives serious disruptions, not just routine incidents.

a) What “service continuity” means at TakeCars

Continuity is not about small issues; it is about major disruption scenarios, such as:

• Payment provider outage
• Platform downtime during peak travel
• Insurance partner failure
• Sudden mass host cancellations
• Regulatory or compliance shutdowns
• Natural disasters affecting travel regions

These events can stop the service entirely if unprepared.

---

b) Continuity vs incident management (critical distinction)

• Incident management
  • Restores service quickly after routine failures
• Service continuity management
  • Prepares for and manages major disruptions

If the service cannot operate at all, continuity plans are required.

---

c) Practical continuity planning for TakeCars

Examples of continuity measures:

• Backup payment providers
• Manual booking or support fallback procedures
• Clear communication templates for mass disruption
• Priority rules for reallocating vehicles
• Data backups and recovery plans

The goal is not perfection, but acceptable service levels under stress.

---

d) Testing and readiness

ITIL stresses that plans must be:

• Documented
• Tested
• Reviewed

Untested plans fail in real crises.

For TakeCars:

• Simulate provider outages
• Simulate peak-season failures
• Review response times and decision paths

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of service continuity management?”

Correct logic:

• Ensure services continue at acceptable levels
• Prepare for major disruptions
• Support recovery and resilience

Answers focusing only on minor incidents are incorrect.

---

3. Key Things to Read / Remember Right Before the Exam

Service continuity management (high probability)

• A service management practice
• Focuses on major disruptions
• Ensures acceptable service levels during crises
• Includes planning, recovery, and testing

---

Common exam traps

• Continuity management handles normal incidents → False
• Continuity plans do not need testing → False
• Continuity management replaces incident management → False

---

One-line memory hook

Service continuity management prepares the organisation to survive major disruptions.

---

---

Service configuration management is the practice of ensuring that accurate and reliable information about the configuration of services and the components that support them is available when needed.

Configuration items are the components that need to be managed in order to deliver a service.

Service configuration management includes identifying configuration items and maintaining information about their relationships.

Accurate configuration information supports effective decision-making and service management activities.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains how TakeCars avoids confusion, errors, and blind spots when operating at scale.

a) What configuration items are at TakeCars

Configuration items (CIs) are anything that must be known and controlled to deliver the service, such as:

• Vehicles
• Hosts
• Bookings
• Insurance policies
• Payment providers
• Support tools
• Pricing and cancellation rules
• Pickup locations

If these are not clearly defined and tracked, service reliability collapses.

---

b) Why configuration accuracy matters in a marketplace

Common TakeCars failures caused by poor configuration data:

• Booking linked to the wrong vehicle
• Insurance rules not matching vehicle type
• Host status unclear (active, suspended, restricted)
• Pricing or deposits applied inconsistently

Service configuration management exists to prevent this.

---

c) Relationships between configuration items (exam nuance)

ITIL explicitly stresses relationships, not just lists.

Examples at TakeCars:

• A booking is linked to:
  • A specific vehicle
  • A specific host
  • A specific insurance product
• A host is linked to:
  • Multiple vehicles
  • Performance metrics
  • Contractual rules

Understanding these relationships enables:

• Faster incident resolution
• Safer change enablement
• Better problem analysis

---

d) Support for other practices

Service configuration management supports:

• Incident management (what is affected?)
• Problem management (what is common?)
• Change enablement (what will be impacted?)
• Service level management (what is being measured?)

This is why ITIL treats it as foundational.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of service configuration management?”

Correct logic:

• Ensure accurate configuration information
• Manage configuration items and relationships
• Support effective service management

Answers focusing only on hardware inventories are incomplete.

---

3. Key Things to Read / Remember Right Before the Exam

Service configuration management (high probability)

• A service management practice
• Manages configuration items (CIs)
• Maintains accurate information and relationships
• Supports decision-making and other practices

---

Common exam traps

• Configuration management is only about IT assets → False
• Configuration management is optional → False
• Configuration data is static → False

---

One-line memory hook

Service configuration management keeps accurate knowledge of what supports the service and how it all connects.

---

Change enablement is the practice of ensuring that changes are assessed, authorised, and scheduled appropriately.

The purpose of change enablement is to maximise the number of successful service and product changes.

Change enablement helps balance the need for change with the need to protect services from disruption.

Changes should be evaluated based on risk, impact, and urgency.

Standard changes may be pre-authorised, while higher-risk changes require additional assessment.

Change enablement supports effective and controlled change across the organisation.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

Change enablement explains how TakeCars evolves safely without breaking live trips, bookings, or trust.

a) What a “change” is at TakeCars

Changes include:

• New pricing rules
• Policy updates (deposits, cancellations)
• Platform feature releases
• Host onboarding changes
• Support workflow changes
• Supplier or payment provider switches

Any change that could affect active bookings is a service risk.

---

b) Purpose: maximise successful change, not block it

Critical ITIL nuance:

• Change enablement is not about stopping change
• It is about enabling change safely

For TakeCars:

• Fast change is good
• Uncontrolled change is dangerous

---

c) Risk-based change evaluation at TakeCars

Standard changes

Low risk, routine, pre-approved.

Examples:

• Updating message templates
• Minor UI text changes
• Adding a predefined extra

These should flow quickly.

---

Normal changes

Medium risk, require assessment.

Examples:

• Changing cancellation rules
• Modifying deposit logic
• Adjusting host eligibility criteria

These need review before release.

---

High-risk changes

Potentially disruptive.

Examples:

• Payment system migration
• Insurance model changes
• Booking flow redesign during peak season

These require careful timing and communication.

---

d) Balancing speed and stability

Without change enablement:

• Bugs hit live trips
• Policies confuse customers
• Support load spikes

With excessive control:

• Improvements stall
• Opportunities are missed

Change enablement balances both.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of change enablement?”

Correct logic:

• Ensure changes are assessed and authorised
• Maximise successful changes
• Minimise disruption

Answers suggesting change enablement exists to prevent change are incorrect.

---

3. Key Things to Read / Remember Right Before the Exam

Change enablement (very high probability)

• A service management practice
• Assesses, authorises, and schedules changes
• Balances change and stability
• Uses risk-based evaluation

---

Common exam traps

• Change enablement blocks change → False
• All changes need the same level of approval → False
• Change enablement focuses only on technology → False

---

One-line memory hook

Change enablement allows change to happen safely without disrupting services.

---