Information Technology and Communications

Building Systems to Track Visitor Behaviour on Digital Platforms

Turn visitor behaviour tracking from a stated policy into a practice your organisation can evidence.

  • 5training days
  • 4modules
  • 8sessions
  • 32topics
View packages and pricesCourse outline
Building Systems to Track Visitor Behaviour on Digital Platforms
5days

About the programme

Course Overview

Security and delivery speed are traded against each other in visitor behaviour tracking whether or not anyone says so. The documentation for this area of technology and systems delivery is accurate only until the next release. The course gives participants a defensible structure for the technology and systems delivery discipline and the judgement to adapt it. Participants gain a realistic view of what visitor behaviour tracking costs and what it returns. It is appropriate for those preparing to take on wider responsibility for the wider technology and systems delivery agenda. The most reliable predictor of sound this strand of technology and systems delivery is whether anyone reviews it when nothing has gone wrong. Sessions alternate between guided analysis of visitor behaviour tracking and supervised application. Teams frequently over-invest in documenting the wider technology and systems delivery agenda and under-invest in testing it. Work concludes with a self-assessment of this area of technology and systems delivery that participants can repeat annually.

Expected Learning Outcomes

  • Prepare a short, evidence-based briefing on visitor behaviour tracking for senior management.

  • Test the organisation's response to visitor behaviour tracking under conditions that are less than ideal.

  • Secure the software supply chain and dependencies within visitor behaviour tracking.

  • Build the deployment pipeline for visitor behaviour tracking so releases are routine rather than events.

  • Control technical debt in visitor behaviour tracking deliberately rather than by neglect.

  • Manage change to visitor behaviour tracking so every release can be rolled back.

  • Design a training and briefing approach that sustains competence in visitor behaviour tracking.

Who Should Attend

  • Procurement and contracting staff whose agreements set obligations around visitor behaviour tracking.

  • Service desk and support leads handling incidents in visitor behaviour tracking.

  • Project managers delivering changes to visitor behaviour tracking.

  • Those responsible for briefing external stakeholders on visitor behaviour tracking.

  • Solution architects designing visitor behaviour tracking.

  • Network and communications engineers supporting visitor behaviour tracking.

Course Modules

Open any module to see its sessions and topics.

01

Visitor behaviour tracking: documentation, support and handover

2 sessions · 8 points

Session 1Making releases of visitor behaviour tracking routine instead of risky

  • Anticipate the objections visitor behaviour tracking will raise and prepare the answers.
  • Confirm that those complying with visitor behaviour tracking understand why it exists.
  • Establish the boundary of visitor behaviour tracking and record what sits outside it.
  • Inventory third-party dependencies inside visitor behaviour tracking and their update status.

Session 2Monitoring visitor behaviour tracking from the user's point of view

  • Test the procedure for visitor behaviour tracking against a realistic scenario.
  • Apply change control to visitor behaviour tracking including emergency changes.
  • Record what was learned when visitor behaviour tracking did not go as planned.
  • Identify the single points of failure in visitor behaviour tracking.
02

Visitor behaviour tracking: monitoring, alerting and observability

2 sessions · 8 points

Session 1Setting availability and recovery targets for visitor behaviour tracking honestly

  • State the availability and recovery objectives for visitor behaviour tracking as numbers.
  • Map the handovers in visitor behaviour tracking between functions and secure them.
  • Set out how exceptions to visitor behaviour tracking are requested and approved.
  • Compare the cost of visitor behaviour tracking with the cost of its absence.

Session 2The cost of visitor behaviour tracking and how to present it

  • Establish who is informed, consulted and accountable in visitor behaviour tracking.
  • Confirm the support model and escalation path for visitor behaviour tracking.
  • Arrange the handover of visitor behaviour tracking so capability survives staff changes.
  • Agree what will be standardised in visitor behaviour tracking and what will not.
03

Visitor behaviour tracking: change control and rollback

2 sessions · 8 points

Session 1Retiring the legacy part of visitor behaviour tracking

  • Prepare the response for the most likely failure in visitor behaviour tracking.
  • Define the trigger that would require visitor behaviour tracking to be redesigned.
  • Test the failover for visitor behaviour tracking rather than assuming it works.
  • Set the review interval for visitor behaviour tracking and who attends.

Session 2Testing visitor behaviour tracking before relying on it

  • Assess the exit route from any cloud or vendor dependency in visitor behaviour tracking.
  • Document the runbook for visitor behaviour tracking to the level a new engineer could use.
  • Reduce the variation in how visitor behaviour tracking is carried out between teams.
  • Set out the decisions in visitor behaviour tracking that require sign-off and by whom.
04

Visitor behaviour tracking: backup, recovery and continuity

2 sessions · 8 points

Session 1Running an incident on visitor behaviour tracking calmly

  • Configure alerting on visitor behaviour tracking that reflects what users experience.
  • Confirm data retention and deletion rules applied within visitor behaviour tracking.
  • Confirm every release of visitor behaviour tracking can be rolled back within a defined time.
  • Set delivery and reliability indicators for visitor behaviour tracking the team trusts.

Session 2What has to be agreed before work on visitor behaviour tracking starts

  • Measure current load on visitor behaviour tracking and project it forward twelve months.
  • Restore a backup of visitor behaviour tracking in a test environment and time it.
  • Review logging on visitor behaviour tracking for coverage and retention.
  • Record the technical debt in visitor behaviour tracking and schedule repayment.

Choose the package that suits you

Silver Package

At least 3 people

USD1,250
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Gold Package

At least 3 people

USD1,850
  • 5-night stay in a 5-star hotel
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Complete your registration

We will contact you within one business day to confirm.

Share this course

🔗 Short link
View packages and prices

✆