Define the scope and boundaries of system administration automation so that responsibility for it is unambiguous.
Building Strategies to Automate Repetitive System Administration Tasks
Develop the judgement and the documentation needed to run system administration automation properly.
📍 Tripoli🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Most outages involving system administration automation are triggered by a change somebody considered routine. Security and delivery speed are traded against each other in the technology and systems delivery discipline whether or not anyone says so. A common pattern is strong design of this area of technology and systems delivery paired with weak follow-through. Applied research in technology and systems delivery consistently shows that early structure around system administration automation reduces downstream rework. The programme works equally well for those formalising the technology and systems delivery capability for the first time and those improving an existing approach. Content is organised around the decisions practitioners actually face in this area of technology and systems delivery, not around theory headings. They leave able to brief senior management on system administration automation in terms that support a decision. The teaching approach is deliberately practical: participants build a technical standard for the technology and systems delivery capability as they go. It closes by agreeing the smallest change to the practice within technology and systems delivery that would make a visible difference.
Expected Learning Outcomes
Manage change to system administration automation so every release can be rolled back.
Verify that improvements to system administration automation have held six months after they were introduced.
Plan capacity for system administration automation against measured growth rather than optimism.
Document system administration automation to the level a new engineer could operate it.
Reduce avoidable variation in how system administration automation is carried out across teams.
Plan the migration or decommissioning of legacy components in system administration automation.
Who Should Attend
Officers preparing reports on system administration automation for boards or oversight committees.
Quality and test engineers verifying system administration automation.
IT managers and service owners responsible for system administration automation.
Technical staff being prepared for supervisory responsibility over system administration automation.
Network and communications engineers supporting system administration automation.
IT governance and audit staff reviewing system administration automation.
Course Modules
System administration automation: capacity, performance and load
2 sessions · 8 pointsSession 1Proving the backup of system administration automation by restoring it
- Write down the assumptions underpinning the approach to system administration automation.
- Inventory third-party dependencies inside system administration automation and their update status.
- Document the runbook for system administration automation to the level a new engineer could use.
- Restore a backup of system administration automation in a test environment and time it.
Session 2What to measure in system administration automation and what to ignore
- Set delivery and reliability indicators for system administration automation the team trusts.
- State the availability and recovery objectives for system administration automation as numbers.
- Configure alerting on system administration automation that reflects what users experience.
- Test the failover for system administration automation rather than assuming it works.
System administration automation: architecture and designing for failure
2 sessions · 8 pointsSession 1Running an incident on system administration automation calmly
- Confirm that reporting on system administration automation reaches the people who can act.
- Confirm data retention and deletion rules applied within system administration automation.
- Review access rights on system administration automation and remove what is no longer needed.
- Review logging on system administration automation for coverage and retention.
Session 2Making releases of system administration automation routine instead of risky
- Apply change control to system administration automation including emergency changes.
- Establish what evidence demonstrates system administration automation is under control.
- Collect evidence on the present handling of system administration automation before proposing changes.
- Run a load test on system administration automation at expected peak plus a margin.
System administration automation: incident response and severity
2 sessions · 8 pointsSession 1Making system administration automation work when resources are constrained
- Establish the boundary of system administration automation and record what sits outside it.
- Identify the single points of failure in system administration automation.
- Agree the smallest change to system administration automation that would be visibly useful.
- Verify six months later that changes to system administration automation have held.
Session 2Monitoring system administration automation from the user's point of view
- Confirm the support model and escalation path for system administration automation.
- Review whether system administration automation is aligned with the objectives of the technical platform.
- Identify the data already collected that bears on system administration automation.
- Set out the decisions in system administration automation that require sign-off and by whom.
System administration automation: backup, recovery and continuity
2 sessions · 8 pointsSession 1Setting availability and recovery targets for system administration automation honestly
- Anticipate the objections system administration automation will raise and prepare the answers.
- Confirm every release of system administration automation can be rolled back within a defined time.
- Estimate the resource system administration automation requires to run as designed.
- Define incident severity levels for system administration automation and the response each triggers.
Session 2Testing system administration automation before relying on it
- Agree the indicators that will show whether system administration automation is improving.
- Agree what will be standardised in system administration automation and what will not.
- Check that records of system administration automation answer the questions likely to be asked.
- Rank the weaknesses in system administration automation by consequence rather than by ease of fixing.
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.