Boards are asking for measurable returns from software-defined network engineering, not demonstrations. The constraint on this aspect of digital and data-driven work is rarely the model or the platform — it is the data and the operating discipline behind it. Exercises escalate in difficulty, ending with the ambiguous situations that make this strand of digital and data-driven work hard in practice. The course gives participants a defensible structure for software-defined network engineering and the judgement to adapt it. The material serves both public bodies and commercial organisations dealing with the digital and data-driven work discipline. They acquire practical criteria for judging when this strand of digital and data-driven work is working and when it is only appearing to. The version of software-defined network engineering described in the manual and the version practised on the floor tend to diverge over time. Benchmarking exercises repeatedly place the practice within digital and data-driven work among the areas with the widest performance spread. Participants leave with a plan for the digital and data-driven work discipline sized to what their organisation can realistically absorb.
Expected Learning Outcomes
✓
Document the decision record for software-defined network engineering so successors understand why it is built this way.
✓
Review contracts and agreements for the obligations they create around software-defined network engineering.
✓
Evaluate the bias, fairness and explainability obligations attaching to software-defined network engineering.
✓
Establish what evidence would demonstrate that software-defined network engineering is under control.
✓
Build a concise delivery roadmap for software-defined network engineering that colleagues can follow without further explanation.
✓
Establish version control and rollback for every component of software-defined network engineering that reaches production.
✓
Define success criteria for software-defined network engineering in business terms before any technology is selected.
Who Should Attend
✓
Solution architects designing how software-defined network engineering fits the existing estate.
✓
Operations managers whose processes are changed by software-defined network engineering.
✓
Public sector officials applying software-defined network engineering within a regulated framework.
✓
Managers with direct responsibility for software-defined network engineering within the transformation programme.
✓
Vendor and contract managers overseeing suppliers involved in software-defined network engineering.
✓
Public sector digital leads applying software-defined network engineering under procurement and privacy rules.
Course Modules
Open any module to see its sessions and topics.
01
Software-defined network engineering: monitoring, drift and operational ownership
2 sessions · 8 points
Session 1Where software-defined network engineering touches systems nobody wants to change
Plan how software-defined network engineering is versioned and how a bad release is rolled back.
Design the pilot for software-defined network engineering so that a negative result is still useful.
Define acceptance criteria for software-defined network engineering in advance.
Set the metrics that will show whether software-defined network engineering is drifting from its intended behaviour.
Session 2The governance software-defined network engineering needs and the governance it does not
Write down the assumptions underpinning the approach to software-defined network engineering.
Test software-defined network engineering against edge cases drawn from real historical records.
Identify the skills the team lacks to operate software-defined network engineering independently.
Build the internal briefing that explains software-defined network engineering to those affected.
02
Software-defined network engineering: business case, scope and the data it depends on
2 sessions · 8 points
Session 1Making software-defined network engineering work when resources are constrained
Assess the regulatory obligations software-defined network engineering triggers in each jurisdiction.
Identify every system software-defined network engineering must read from or write to.
Test the procedure for software-defined network engineering against a realistic scenario.
Specify the fallback path when software-defined network engineering is unavailable.
Session 2Testing software-defined network engineering before relying on it
Agree the indicators that will show whether software-defined network engineering is improving.
Reduce the variation in how software-defined network engineering is carried out between teams.
Prepare the response for the most likely failure in software-defined network engineering.
Measure the current quality of the data feeding software-defined network engineering before assuming it is usable.
03
Software-defined network engineering: people, skills and the change that follows
2 sessions · 8 points
Session 1Reading the true cost of running software-defined network engineering
Identify where judgement in software-defined network engineering is legitimate and where it is not.
Agree the smallest change to software-defined network engineering that would be visibly useful.
Classify the data in software-defined network engineering and apply access controls that match the classification.
Set escalation thresholds for software-defined network engineering that work out of hours.
Session 2Making software-defined network engineering secure without making it unusable
Prepare the summary of software-defined network engineering that senior management will read.
Identify the data already collected that bears on software-defined network engineering.
Decide which legacy process software-defined network engineering retires, and set the date.
Verify that software-defined network engineering still performs when input volume doubles unexpectedly.
04
Software-defined network engineering: governance, ethics and explainability
2 sessions · 8 points
Session 1The decisions in software-defined network engineering that cannot be delegated
Record the reasoning behind each architectural choice in software-defined network engineering.
Confirm the retention and deletion rules applied to data inside software-defined network engineering.
Set out how exceptions to software-defined network engineering are requested and approved.
Estimate the resource software-defined network engineering requires to run as designed.
Session 2The pilot that actually settles the argument about software-defined network engineering
Establish what evidence demonstrates software-defined network engineering is under control.
Build the user briefing that explains what software-defined network engineering does and does not decide.
Estimate compute and licensing cost for software-defined network engineering at expected and at peak load.
Remove steps in software-defined network engineering that add effort without adding assurance.
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.
