Information Technology and Communications

Building Integrated Enterprise Architecture Strategies for Information Technology

A senior-level treatment of enterprise architecture strategy, focused on what changes outcomes.

  • 5training days
  • 4modules
  • 8sessions
  • 32topics
View packages and pricesCourse outline
Building Integrated Enterprise Architecture Strategies for Information Technology
5days

About the programme

Course Overview

Systems supporting enterprise architecture strategy fail in ways that are obvious afterwards and invisible before. Availability targets for this strand of technology and systems delivery are commercial commitments, whatever the engineering team calls them. Participants finish able to explain the practice within technology and systems delivery to a non-specialist audience without losing precision. Progress on enterprise architecture strategy is usually lost in the gap between approval and execution. Organisations that document this strand of technology and systems delivery properly resolve disputes about it far more quickly. The course sets out a working method for the practice within technology and systems delivery that participants can apply the week they return. Participants come from operational and oversight roles, and both perspectives on enterprise architecture strategy are used deliberately. The programme uses small-group work so that each participant's treatment of this part of technology and systems delivery is examined, not just described. Participants leave with a plan for the wider technology and systems delivery agenda sized to what their organisation can realistically absorb.

Expected Learning Outcomes

  • Plan capacity for enterprise architecture strategy against measured growth rather than optimism.

  • Assess and manage third-party and cloud dependencies in enterprise architecture strategy.

  • Identify the failure points in enterprise architecture strategy most likely to cause loss, and control them first.

  • Control technical debt in enterprise architecture strategy deliberately rather than by neglect.

  • Review contracts and agreements for the obligations they create around enterprise architecture strategy.

  • Design backup and recovery for enterprise architecture strategy and prove it by restoring.

  • Anticipate the objections that enterprise architecture strategy will attract internally and answer them in advance.

Who Should Attend

  • Compliance and governance staff whose remit includes enterprise architecture strategy.

  • Database administrators managing data within enterprise architecture strategy.

  • Vendor managers overseeing suppliers involved in enterprise architecture strategy.

  • Those responsible for briefing external stakeholders on enterprise architecture strategy.

  • Project managers delivering changes to enterprise architecture strategy.

  • Solution architects designing enterprise architecture strategy.

Course Modules

Open any module to see its sessions and topics.

01

Enterprise architecture strategy: architecture and designing for failure

2 sessions · 8 points

Session 1Sizing capacity for enterprise architecture strategy on measured growth

  • Restore a backup of enterprise architecture strategy in a test environment and time it.
  • Set the review interval for enterprise architecture strategy and who attends.
  • Confirm data retention and deletion rules applied within enterprise architecture strategy.
  • Test the procedure for enterprise architecture strategy against a realistic scenario.

Session 2Running an incident on enterprise architecture strategy calmly

  • Decide what will be stopped to create capacity for enterprise architecture strategy.
  • Configure alerting on enterprise architecture strategy that reflects what users experience.
  • Set out how exceptions to enterprise architecture strategy are requested and approved.
  • Assess the exit route from any cloud or vendor dependency in enterprise architecture strategy.
02

Enterprise architecture strategy: documentation, support and handover

2 sessions · 8 points

Session 1What to measure in enterprise architecture strategy and what to ignore

  • Draft the minimum viable technical standard for enterprise architecture strategy.
  • Define incident severity levels for enterprise architecture strategy and the response each triggers.
  • Confirm every release of enterprise architecture strategy can be rolled back within a defined time.
  • Record what was learned when enterprise architecture strategy did not go as planned.

Session 2Designing enterprise architecture strategy around how it will fail

  • Map the handovers in enterprise architecture strategy between functions and secure them.
  • Test the failover for enterprise architecture strategy rather than assuming it works.
  • Record the technical debt in enterprise architecture strategy and schedule repayment.
  • Apply change control to enterprise architecture strategy including emergency changes.
03

Enterprise architecture strategy: change control and rollback

2 sessions · 8 points

Session 1Comparing enterprise architecture strategy with recognised practice

  • Identify where judgement in enterprise architecture strategy is legitimate and where it is not.
  • Anticipate the objections enterprise architecture strategy will raise and prepare the answers.
  • Review whether enterprise architecture strategy is aligned with the objectives of the technical platform.
  • Distinguish symptoms from causes when enterprise architecture strategy underperforms.

Session 2Building the method for enterprise architecture strategy step by step

  • Measure current load on enterprise architecture strategy and project it forward twelve months.
  • Set escalation thresholds for enterprise architecture strategy that work out of hours.
  • Review access rights on enterprise architecture strategy and remove what is no longer needed.
  • Verify six months later that changes to enterprise architecture strategy have held.
04

Enterprise architecture strategy: capacity, performance and load

2 sessions · 8 points

Session 1Documenting enterprise architecture strategy so someone else can operate it

  • Identify the single points of failure in enterprise architecture strategy.
  • Close out actions on enterprise architecture strategy rather than leaving them open indefinitely.
  • Confirm the support model and escalation path for enterprise architecture strategy.
  • Document the runbook for enterprise architecture strategy to the level a new engineer could use.

Session 2Making releases of enterprise architecture strategy routine instead of risky

  • Run a load test on enterprise architecture strategy at expected peak plus a margin.
  • Assign responsibility for keeping documentation of enterprise architecture strategy current.
  • Record the rationale for each significant choice made about enterprise architecture strategy.
  • Set delivery and reliability indicators for enterprise architecture strategy the team trusts.

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

✆