Diagnose whether a problem in technical knowledge bases is one of design, resourcing or discipline.
Building Comprehensive Knowledge Bases for Common Technical Problems
Move technical knowledge bases from general awareness to a repeatable, reviewable practice.
📍 Tripoli🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Availability targets for technical knowledge bases are commercial commitments, whatever the engineering team calls them. The documentation for the technology and systems delivery capability is accurate only until the next release. The programme takes participants through the technology and systems delivery discipline end to end, from framing the problem to closing it out. Exercises escalate in difficulty, ending with the ambiguous situations that make technical knowledge bases hard in practice. Organisations that document this area of technology and systems delivery properly resolve disputes about it far more quickly. Buying a tool rarely fixes the technology and systems delivery discipline; the underlying capability has to be built internally first. Participants gain a clear basis for measuring what technical knowledge bases has actually achieved. It is pitched for practitioners with responsibility for the practice within technology and systems delivery, not for observers of it. It closes by agreeing the smallest change to this part of technology and systems delivery that would make a visible difference.
Expected Learning Outcomes
Manage change to technical knowledge bases so every release can be rolled back.
Secure the software supply chain and dependencies within technical knowledge bases.
Apply access control and least privilege throughout technical knowledge bases.
Test technical knowledge bases under realistic load before it meets real load.
Handle the trade-offs in technical knowledge bases between speed, cost and assurance explicitly rather than implicitly.
Assign clear ownership for each element of technical knowledge bases across the functions involved.
Who Should Attend
Managers with direct responsibility for technical knowledge bases within the technical platform.
Public sector officials applying technical knowledge bases within a regulated framework.
Software engineers and technical leads building technical knowledge bases.
Vendor managers overseeing suppliers involved in technical knowledge bases.
IT governance and audit staff reviewing technical knowledge bases.
Network and communications engineers supporting technical knowledge bases.
Course Modules
Technical knowledge bases: requirements, targets and service levels
2 sessions · 8 pointsSession 1Retiring the legacy part of technical knowledge bases
- Review whether technical knowledge bases is aligned with the objectives of the technical platform.
- Test the failover for technical knowledge bases rather than assuming it works.
- Review access rights on technical knowledge bases and remove what is no longer needed.
- Restore a backup of technical knowledge bases in a test environment and time it.
Session 2Least privilege in technical knowledge bases without blocking the work
- Configure alerting on technical knowledge bases that reflects what users experience.
- Run a load test on technical knowledge bases at expected peak plus a margin.
- Define incident severity levels for technical knowledge bases and the response each triggers.
- Identify the single points of failure in technical knowledge bases.
Technical knowledge bases: incident response and severity
2 sessions · 8 pointsSession 1Moving technical knowledge bases from approval to execution
- Confirm every release of technical knowledge bases can be rolled back within a defined time.
- Set escalation thresholds for technical knowledge bases that work out of hours.
- Draft the minimum viable technical standard for technical knowledge bases.
- Apply change control to technical knowledge bases including emergency changes.
Session 2Setting availability and recovery targets for technical knowledge bases honestly
- Record what was learned when technical knowledge bases did not go as planned.
- Confirm that contractual obligations around technical knowledge bases are understood.
- State the availability and recovery objectives for technical knowledge bases as numbers.
- Compare the cost of technical knowledge bases with the cost of its absence.
Technical knowledge bases: backup, recovery and continuity
2 sessions · 8 pointsSession 1Keeping technical knowledge bases alive after the initial push
- Check that records of technical knowledge bases answer the questions likely to be asked.
- Establish what evidence demonstrates technical knowledge bases is under control.
- Rank the weaknesses in technical knowledge bases by consequence rather than by ease of fixing.
- Record the technical debt in technical knowledge bases and schedule repayment.
Session 2Reviewing technical knowledge bases when nothing has gone wrong
- Test the procedure for technical knowledge bases against a realistic scenario.
- Confirm data retention and deletion rules applied within technical knowledge bases.
- Identify the data already collected that bears on technical knowledge bases.
- Document the runbook for technical knowledge bases to the level a new engineer could use.
Technical knowledge bases: security, identity and least privilege
2 sessions · 8 pointsSession 1Designing technical knowledge bases around how it will fail
- Check that technical knowledge bases still works when volumes rise unexpectedly.
- Identify where judgement in technical knowledge bases is legitimate and where it is not.
- Measure current load on technical knowledge bases and project it forward twelve months.
- Write down the assumptions underpinning the approach to technical knowledge bases.
Session 2Making releases of technical knowledge bases routine instead of risky
- Collect evidence on the present handling of technical knowledge bases before proposing changes.
- Inventory third-party dependencies inside technical knowledge bases and their update status.
- Agree the indicators that will show whether technical knowledge bases is improving.
- Confirm the support model and escalation path for technical knowledge bases.
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.