Prepare the human side of low-code mobile applications: who is retrained, who is redeployed, and when they are told.
Building Enterprise Mobile Applications with Low-Code Development Tools
Turn low-code mobile applications from a stated policy into a practice your organisation can evidence.
📍 Istanbul🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Technology choices around low-code mobile applications are easy to reverse on paper and expensive to reverse in practice. The distance between a working prototype of this aspect of digital and data-driven work and a system the business can depend on is where most budgets disappear. It is designed for mixed groups, so that the practice within digital and data-driven work is examined from more than one functional angle. Most organisations already have a policy on low-code mobile applications; far fewer can show it working. Exercises escalate in difficulty, ending with the ambiguous situations that make this part of digital and data-driven work hard in practice. Benchmarking exercises repeatedly place this area of digital and data-driven work among the areas with the widest performance spread. It treats low-code mobile applications as an operating discipline and equips participants to run it as one. The outcome is a practitioner who can hold a position on this strand of digital and data-driven work and revise it on evidence. The programme ends where implementation begins, with the wider digital and data-driven work agenda broken into steps someone can start on Monday.
Expected Learning Outcomes
Document the decision record for low-code mobile applications so successors understand why it is built this way.
Plan the migration path for low-code mobile applications without an extended outage or a parallel-running trap.
Verify that improvements to low-code mobile applications have held six months after they were introduced.
Evaluate the bias, fairness and explainability obligations attaching to low-code mobile applications.
Anticipate the objections that low-code mobile applications will attract internally and answer them in advance.
Structure records of low-code mobile applications so that they answer the questions an auditor will actually ask.
Who Should Attend
Anyone whose accountability for low-code mobile applications exceeds their current formal training in it.
Technology and digital transformation managers leading low-code mobile applications.
Product owners prioritising the roadmap for low-code mobile applications.
Programme managers coordinating delivery of low-code mobile applications across teams.
Solution architects designing how low-code mobile applications fits the existing estate.
Team leaders and supervisors who put low-code mobile applications into practice day to day.
Course Modules
Low-code mobile applications: monitoring, drift and operational ownership
2 sessions · 8 pointsSession 1The pilot that actually settles the argument about low-code mobile applications
- Define the exit route from the supplier supporting low-code mobile applications.
- Assess the regulatory obligations low-code mobile applications triggers in each jurisdiction.
- Decide which legacy process low-code mobile applications retires, and set the date.
- Anticipate the objections low-code mobile applications will raise and prepare the answers.
Session 2Comparing low-code mobile applications with recognised practice
- Prepare the response for the most likely failure in low-code mobile applications.
- Name a single owner for each element of low-code mobile applications.
- Confirm that contractual obligations around low-code mobile applications are understood.
- Confirm that reporting on low-code mobile applications reaches the people who can act.
Low-code mobile applications: vendor selection and avoiding lock-in
2 sessions · 8 pointsSession 1What has to be agreed before work on low-code mobile applications starts
- Measure the current quality of the data feeding low-code mobile applications before assuming it is usable.
- Identify the skills the team lacks to operate low-code mobile applications independently.
- Decide what will be stopped to create capacity for low-code mobile applications.
- Record the reasoning behind each architectural choice in low-code mobile applications.
Session 2Sizing low-code mobile applications honestly before committing budget
- Identify every system low-code mobile applications must read from or write to.
- Plan how low-code mobile applications is versioned and how a bad release is rolled back.
- Confirm that those complying with low-code mobile applications understand why it exists.
- Record what was learned when low-code mobile applications did not go as planned.
Low-code mobile applications: architecture, integration and the existing estate
2 sessions · 8 pointsSession 1The governance low-code mobile applications needs and the governance it does not
- Identify single points of dependency in low-code mobile applications and reduce them.
- List the data sources low-code mobile applications consumes and confirm each has a named owner.
- Specify the fallback path when low-code mobile applications is unavailable.
- Test low-code mobile applications against edge cases drawn from real historical records.
Session 2Explaining low-code mobile applications to people whose jobs it changes
- Set out the decisions in low-code mobile applications that require sign-off and by whom.
- Record the rationale for each significant choice made about low-code mobile applications.
- Identify where judgement in low-code mobile applications is legitimate and where it is not.
- Agree who is on call for low-code mobile applications outside working hours.
Low-code mobile applications: governance, ethics and explainability
2 sessions · 8 pointsSession 1Building the method for low-code mobile applications step by step
- Classify the data in low-code mobile applications and apply access controls that match the classification.
- Estimate compute and licensing cost for low-code mobile applications at expected and at peak load.
- Collect evidence on the present handling of low-code mobile applications before proposing changes.
- Build the user briefing that explains what low-code mobile applications does and does not decide.
Session 2Proving low-code mobile applications paid for itself
- Reduce the variation in how low-code mobile applications is carried out between teams.
- Review whether low-code mobile applications is aligned with the objectives of the transformation programme.
- Set the review interval for low-code mobile applications and who attends.
- Set the metrics that will show whether low-code mobile applications is drifting from its intended behaviour.
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.