Establish monitoring and alerting on cross-platform mobile development that reflects user experience.
Designing Cross-Platform Application Development Strategies
Learn to design, measure and defend your organisation's approach to cross-platform mobile development.
📍 Tripoli🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Most outages involving cross-platform mobile development are triggered by a change somebody considered routine. The documentation for this aspect of technology and systems delivery is accurate only until the next release. Field experience suggests that the barrier to better this strand of technology and systems delivery is rarely technical. Participants test their assumptions about cross-platform mobile development against scenarios designed to break weak ones. They acquire practical criteria for judging when this aspect of technology and systems delivery is working and when it is only appearing to. It is written for people who have to make the technology and systems delivery discipline work with the resources they already have. The programme takes participants through cross-platform mobile development end to end, from framing the problem to closing it out. The difficulty is not agreeing that this part of technology and systems delivery matters — it is deciding what to stop doing to make room for it. The programme ends where implementation begins, with the technology and systems delivery capability broken into steps someone can start on Monday.
Expected Learning Outcomes
Establish escalation routes for cross-platform mobile development that work outside normal hours.
Structure the service desk and support model for cross-platform mobile development.
Plan capacity for cross-platform mobile development against measured growth rather than optimism.
Assess and manage third-party and cloud dependencies in cross-platform mobile development.
Document decisions about cross-platform mobile development in a form that remains useful after the people change.
Establish what evidence would demonstrate that cross-platform mobile development is under control.
Who Should Attend
IT governance and audit staff reviewing cross-platform mobile development.
Network and communications engineers supporting cross-platform mobile development.
Information security specialists protecting cross-platform mobile development.
Quality and test engineers verifying cross-platform mobile development.
Public sector officials applying cross-platform mobile development within a regulated framework.
Coordinators responsible for keeping records and documentation of cross-platform mobile development current.
Course Modules
Cross-platform mobile development: security, identity and least privilege
2 sessions · 8 pointsSession 1Dependencies and supply chain risk in cross-platform mobile development
- Rehearse the briefing on cross-platform mobile development that would follow an incident.
- Close out actions on cross-platform mobile development rather than leaving them open indefinitely.
- Define acceptance criteria for cross-platform mobile development in advance.
- Check that records of cross-platform mobile development answer the questions likely to be asked.
Session 2Comparing cross-platform mobile development with recognised practice
- Record the technical debt in cross-platform mobile development and schedule repayment.
- Define incident severity levels for cross-platform mobile development and the response each triggers.
- Distinguish symptoms from causes when cross-platform mobile development underperforms.
- Prepare the summary of cross-platform mobile development that senior management will read.
Cross-platform mobile development: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Proving the backup of cross-platform mobile development by restoring it
- State the availability and recovery objectives for cross-platform mobile development as numbers.
- Inventory third-party dependencies inside cross-platform mobile development and their update status.
- Verify six months later that changes to cross-platform mobile development have held.
- Set delivery and reliability indicators for cross-platform mobile development the team trusts.
Session 2Least privilege in cross-platform mobile development without blocking the work
- Set escalation thresholds for cross-platform mobile development that work out of hours.
- Plan the sequence in which improvements to cross-platform mobile development will be introduced.
- Decide what will be stopped to create capacity for cross-platform mobile development.
- Measure current load on cross-platform mobile development and project it forward twelve months.
Cross-platform mobile development: documentation, support and handover
2 sessions · 8 pointsSession 1Documenting cross-platform mobile development so someone else can operate it
- Confirm the support model and escalation path for cross-platform mobile development.
- Configure alerting on cross-platform mobile development that reflects what users experience.
- Assess the exit route from any cloud or vendor dependency in cross-platform mobile development.
- Set out how exceptions to cross-platform mobile development are requested and approved.
Session 2Reviewing cross-platform mobile development when nothing has gone wrong
- Agree the indicators that will show whether cross-platform mobile development is improving.
- Document the runbook for cross-platform mobile development to the level a new engineer could use.
- Confirm that reporting on cross-platform mobile development reaches the people who can act.
- Estimate the resource cross-platform mobile development requires to run as designed.
Cross-platform mobile development: build, pipeline and release discipline
2 sessions · 8 pointsSession 1The decisions in cross-platform mobile development that cannot be delegated
- Rank the weaknesses in cross-platform mobile development by consequence rather than by ease of fixing.
- Confirm every release of cross-platform mobile development can be rolled back within a defined time.
- Collect evidence on the present handling of cross-platform mobile development before proposing changes.
- Confirm data retention and deletion rules applied within cross-platform mobile development.
Session 2Designing cross-platform mobile development around how it will fail
- Run a load test on cross-platform mobile development at expected peak plus a margin.
- Test the failover for cross-platform mobile development rather than assuming it works.
- Restore a backup of cross-platform mobile development in a test environment and time it.
- Identify the single points of failure in cross-platform mobile development.
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.