Plan the handover of software-defined networking so that capability is not lost when key staff move on.
Building Software-Defined Network Management Systems
Learn to design, measure and defend your organisation's approach to software-defined networking.
📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Availability targets for software-defined networking are commercial commitments, whatever the engineering team calls them. Technical debt in this aspect of technology and systems delivery is borrowed against future delivery capacity, at compound interest. Participants who influence the technology and systems delivery capability without directly controlling it will find the content directly usable. Moving software-defined networking from written policy into daily practice is not achieved by a single decision. Comparative studies of the practice within technology and systems delivery across sectors find the same handful of failure points recurring. The outcome is a practitioner who can hold a position on the wider technology and systems delivery agenda and revise it on evidence. Sessions alternate between guided analysis of software-defined networking and supervised application. It treats this area of technology and systems delivery as an operating discipline and equips participants to run it as one. It ends with a prioritised list of changes to this strand of technology and systems delivery that the participant is prepared to defend internally.
Expected Learning Outcomes
Establish escalation routes for software-defined networking that work outside normal hours.
Plan the migration or decommissioning of legacy components in software-defined networking.
Design the architecture of software-defined networking around its failure modes, not only its happy path.
Assess and manage third-party and cloud dependencies in software-defined networking.
Integrate software-defined networking into existing management routines rather than running it separately.
Design backup and recovery for software-defined networking and prove it by restoring.
Who Should Attend
Quality staff verifying that software-defined networking performs as designed.
Network and communications engineers supporting software-defined networking.
Service desk and support leads handling incidents in software-defined networking.
Infrastructure and platform engineers operating software-defined networking.
Team leaders and supervisors who put software-defined networking into practice day to day.
IT managers and service owners responsible for software-defined networking.
Course Modules
Software-defined networking: requirements, targets and service levels
2 sessions · 8 pointsSession 1Running an incident on software-defined networking calmly
- Write down the assumptions underpinning the approach to software-defined networking.
- Define the trigger that would require software-defined networking to be redesigned.
- Plan the sequence in which improvements to software-defined networking will be introduced.
- Set delivery and reliability indicators for software-defined networking the team trusts.
Session 2Designing software-defined networking around how it will fail
- Confirm every release of software-defined networking can be rolled back within a defined time.
- Measure current load on software-defined networking and project it forward twelve months.
- Distinguish symptoms from causes when software-defined networking underperforms.
- Decide what will be stopped to create capacity for software-defined networking.
Software-defined networking: build, pipeline and release discipline
2 sessions · 8 pointsSession 1Keeping software-defined networking alive after the initial push
- Confirm the support model and escalation path for software-defined networking.
- Name a single owner for each element of software-defined networking.
- Identify the data already collected that bears on software-defined networking.
- Plan the decommissioning of the legacy component software-defined networking replaces.
Session 2Making releases of software-defined networking routine instead of risky
- Run a load test on software-defined networking at expected peak plus a margin.
- Apply change control to software-defined networking including emergency changes.
- Document the runbook for software-defined networking to the level a new engineer could use.
- Set escalation thresholds for software-defined networking that work out of hours.
Software-defined networking: security, identity and least privilege
2 sessions · 8 pointsSession 1What has to be agreed before work on software-defined networking starts
- State the availability and recovery objectives for software-defined networking as numbers.
- Review access rights on software-defined networking and remove what is no longer needed.
- Arrange the handover of software-defined networking so capability survives staff changes.
- Assess the exit route from any cloud or vendor dependency in software-defined networking.
Session 2The cost of software-defined networking and how to present it
- Map the handovers in software-defined networking between functions and secure them.
- Configure alerting on software-defined networking that reflects what users experience.
- Reduce the variation in how software-defined networking is carried out between teams.
- Confirm data retention and deletion rules applied within software-defined networking.
Software-defined networking: documentation, support and handover
2 sessions · 8 pointsSession 1Monitoring software-defined networking from the user's point of view
- Define incident severity levels for software-defined networking and the response each triggers.
- Close out actions on software-defined networking rather than leaving them open indefinitely.
- Set out the decisions in software-defined networking that require sign-off and by whom.
- Inventory third-party dependencies inside software-defined networking and their update status.
Session 2Retiring the legacy part of software-defined networking
- Review logging on software-defined networking for coverage and retention.
- Establish what evidence demonstrates software-defined networking is under control.
- Check that records of software-defined networking answer the questions likely to be asked.
- Set out how exceptions to software-defined networking are requested and approved.
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.