Manage change to enterprise reference architecture so every release can be rolled back.
Designing Reference Models for Enterprise Systems Architecture
A working programme in enterprise reference architecture for managers who have to deliver with existing resources.
📍 Cairo🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Availability targets for enterprise reference architecture are commercial commitments, whatever the engineering team calls them. The documentation for this strand of technology and systems delivery is accurate only until the next release. The programme builds the judgement to know which parts of this part of technology and systems delivery to standardise and which to leave flexible. Each session closes with a decision the participant must justify about enterprise reference architecture in their own setting. The course gives participants a defensible structure for this strand of technology and systems delivery and the judgement to adapt it. The most reliable predictor of sound the technology and systems delivery discipline is whether anyone reviews it when nothing has gone wrong. It suits anyone whose decisions touch enterprise reference architecture, in large organisations and small ones alike. Teams frequently over-invest in documenting this strand of technology and systems delivery and under-invest in testing it. The course ends by identifying what the participant will stop doing to make the practice within technology and systems delivery sustainable.
Expected Learning Outcomes
Secure the software supply chain and dependencies within enterprise reference architecture.
Measure delivery and reliability of enterprise reference architecture with indicators teams trust.
Document decisions about enterprise reference architecture in a form that remains useful after the people change.
Estimate what enterprise reference architecture costs to run properly, and what is lost when it is not.
Establish monitoring and alerting on enterprise reference architecture that reflects user experience.
Set the minimum documentation for enterprise reference architecture that is genuinely necessary, and stop there.
Who Should Attend
Information security specialists protecting enterprise reference architecture.
Coordinators responsible for keeping records and documentation of enterprise reference architecture current.
IT managers and service owners responsible for enterprise reference architecture.
Staff seconded into improvement work on enterprise reference architecture.
Service desk and support leads handling incidents in enterprise reference architecture.
Network and communications engineers supporting enterprise reference architecture.
Course Modules
Enterprise reference architecture: build, pipeline and release discipline
2 sessions · 8 pointsSession 1Where enterprise reference architecture typically breaks, and why
- Establish who is informed, consulted and accountable in enterprise reference architecture.
- Rehearse the briefing on enterprise reference architecture that would follow an incident.
- Agree the smallest change to enterprise reference architecture that would be visibly useful.
- Build the competence framework that supports enterprise reference architecture.
Session 2Building the method for enterprise reference architecture step by step
- Name a single owner for each element of enterprise reference architecture.
- Assess the exit route from any cloud or vendor dependency in enterprise reference architecture.
- Set escalation thresholds for enterprise reference architecture that work out of hours.
- Define acceptance criteria for enterprise reference architecture in advance.
Enterprise reference architecture: incident response and severity
2 sessions · 8 pointsSession 1Least privilege in enterprise reference architecture without blocking the work
- Draft the minimum viable technical standard for enterprise reference architecture.
- Identify the single points of failure in enterprise reference architecture.
- Test the procedure for enterprise reference architecture against a realistic scenario.
- Reduce the variation in how enterprise reference architecture is carried out between teams.
Session 2Making releases of enterprise reference architecture routine instead of risky
- Assign responsibility for keeping documentation of enterprise reference architecture current.
- Confirm data retention and deletion rules applied within enterprise reference architecture.
- Identify single points of dependency in enterprise reference architecture and reduce them.
- Review access rights on enterprise reference architecture and remove what is no longer needed.
Enterprise reference architecture: security, identity and least privilege
2 sessions · 8 pointsSession 1Sizing capacity for enterprise reference architecture on measured growth
- Check that enterprise reference architecture still works when volumes rise unexpectedly.
- Set delivery and reliability indicators for enterprise reference architecture the team trusts.
- Document the runbook for enterprise reference architecture to the level a new engineer could use.
- Test the failover for enterprise reference architecture rather than assuming it works.
Session 2Documenting enterprise reference architecture so someone else can operate it
- Confirm every release of enterprise reference architecture can be rolled back within a defined time.
- State the availability and recovery objectives for enterprise reference architecture as numbers.
- Measure current load on enterprise reference architecture and project it forward twelve months.
- Record the technical debt in enterprise reference architecture and schedule repayment.
Enterprise reference architecture: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Building lasting competence in enterprise reference architecture
- Define incident severity levels for enterprise reference architecture and the response each triggers.
- Run a load test on enterprise reference architecture at expected peak plus a margin.
- Configure alerting on enterprise reference architecture that reflects what users experience.
- Confirm the support model and escalation path for enterprise reference architecture.
Session 2Retiring the legacy part of enterprise reference architecture
- Establish the boundary of enterprise reference architecture and record what sits outside it.
- Arrange the handover of enterprise reference architecture so capability survives staff changes.
- Define the trigger that would require enterprise reference architecture to be redesigned.
- Inventory third-party dependencies inside enterprise reference architecture and their update status.
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.