Building Progressive Web Applications That Work Offline

A working programme in progressive web applications for managers who have to deliver with existing resources.

📍 Abu Dhabi🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points

Course Overview

Most outages involving progressive web applications are triggered by a change somebody considered routine. Systems supporting this aspect of technology and systems delivery fail in ways that are obvious afterwards and invisible before. The programme works equally well for those formalising the practice within technology and systems delivery for the first time and those improving an existing approach. Comparative studies of progressive web applications across sectors find the same handful of failure points recurring. A common pattern is strong design of the technology and systems delivery discipline paired with weak follow-through. They gain the ability to sequence improvements to this strand of technology and systems delivery in an order their organisation can absorb. The programme takes participants through progressive web applications end to end, from framing the problem to closing it out. Sessions alternate between guided analysis of the technology and systems delivery capability and supervised application. The closing exercise tests whether the participant's plan for this area of technology and systems delivery survives a hostile question.

Expected Learning Outcomes

01

Apply a repeatable review cycle to progressive web applications and act on what it produces.

02

Plan capacity for progressive web applications against measured growth rather than optimism.

03

Control technical debt in progressive web applications deliberately rather than by neglect.

04

Measure delivery and reliability of progressive web applications with indicators teams trust.

05

Test the organisation's response to progressive web applications under conditions that are less than ideal.

06

Secure the software supply chain and dependencies within progressive web applications.

07

Estimate what progressive web applications costs to run properly, and what is lost when it is not.

Who Should Attend

01

Solution architects designing progressive web applications.

02

Vendor managers overseeing suppliers involved in progressive web applications.

03

IT governance and audit staff reviewing progressive web applications.

04

IT managers and service owners responsible for progressive web applications.

05

Consultants and advisers supporting clients on progressive web applications.

06

Project and programme managers whose delivery depends on progressive web applications.

Course Modules

01

Progressive web applications: change control and rollback

2 sessions · 8 points

Session 1Sizing capacity for progressive web applications on measured growth

  • Identify the single points of failure in progressive web applications.
  • Identify where judgement in progressive web applications is legitimate and where it is not.
  • State the availability and recovery objectives for progressive web applications as numbers.
  • Agree what will be standardised in progressive web applications and what will not.

Session 2Making releases of progressive web applications routine instead of risky

  • Apply change control to progressive web applications including emergency changes.
  • Record what was learned when progressive web applications did not go as planned.
  • Measure current load on progressive web applications and project it forward twelve months.
  • Confirm data retention and deletion rules applied within progressive web applications.
02

Progressive web applications: documentation, support and handover

2 sessions · 8 points

Session 1Retiring the legacy part of progressive web applications

  • Review logging on progressive web applications for coverage and retention.
  • Configure alerting on progressive web applications that reflects what users experience.
  • Define the trigger that would require progressive web applications to be redesigned.
  • Prepare the response for the most likely failure in progressive web applications.

Session 2Dependencies and supply chain risk in progressive web applications

  • Decide what will be stopped to create capacity for progressive web applications.
  • Review access rights on progressive web applications and remove what is no longer needed.
  • Establish what evidence demonstrates progressive web applications is under control.
  • Set delivery and reliability indicators for progressive web applications the team trusts.
03

Progressive web applications: incident response and severity

2 sessions · 8 points

Session 1The decisions in progressive web applications that cannot be delegated

  • Reduce the variation in how progressive web applications is carried out between teams.
  • Test the failover for progressive web applications rather than assuming it works.
  • Record the technical debt in progressive web applications and schedule repayment.
  • Assign responsibility for keeping documentation of progressive web applications current.

Session 2Running an incident on progressive web applications calmly

  • Set the review interval for progressive web applications and who attends.
  • Define incident severity levels for progressive web applications and the response each triggers.
  • Assess the exit route from any cloud or vendor dependency in progressive web applications.
  • Compare the cost of progressive web applications with the cost of its absence.
04

Progressive web applications: architecture and designing for failure

2 sessions · 8 points

Session 1Comparing progressive web applications with recognised practice

  • Close out actions on progressive web applications rather than leaving them open indefinitely.
  • Document the runbook for progressive web applications to the level a new engineer could use.
  • Restore a backup of progressive web applications in a test environment and time it.
  • Identify single points of dependency in progressive web applications and reduce them.

Session 2Getting other functions to support progressive web applications

  • Record the rationale for each significant choice made about progressive web applications.
  • Set escalation thresholds for progressive web applications that work out of hours.
  • Confirm every release of progressive web applications can be rolled back within a defined time.
  • Map the handovers in progressive web applications between functions and secure them.

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.