Build the deployment pipeline for technical debt management so releases are routine rather than events.
Building Strategies to Manage Technical Debt in Large Projects
A senior-level treatment of technical debt management, focused on what changes outcomes.
📍 Cairo🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Security and delivery speed are traded against each other in technical debt management whether or not anyone says so. Technical debt in this part of technology and systems delivery is borrowed against future delivery capacity, at compound interest. Content is organised around the decisions practitioners actually face in the technology and systems delivery capability, not around theory headings. Field experience suggests that the barrier to better technical debt management is rarely technical. Ambition around this aspect of technology and systems delivery outruns capacity unless the sequencing is deliberate. The programme suits teams tackling this area of technology and systems delivery together as readily as individuals attending alone. Participants test their assumptions about technical debt management against scenarios designed to break weak ones. They acquire practical criteria for judging when the technology and systems delivery discipline is working and when it is only appearing to. The final module sets out how progress on this aspect of technology and systems delivery will be evidenced six months later.
Expected Learning Outcomes
Communicate the purpose of technical debt management to those who have to comply with it.
Define the scope and boundaries of technical debt management so that responsibility for it is unambiguous.
Measure delivery and reliability of technical debt management with indicators teams trust.
Plan capacity for technical debt management against measured growth rather than optimism.
Estimate what technical debt management costs to run properly, and what is lost when it is not.
Apply access control and least privilege throughout technical debt management.
Who Should Attend
Network and communications engineers supporting technical debt management.
Operations staff who encounter the consequences of technical debt management directly.
Project managers delivering changes to technical debt management.
Quality and test engineers verifying technical debt management.
Software engineers and technical leads building technical debt management.
Staff seconded into improvement work on technical debt management.
Course Modules
Technical debt management: build, pipeline and release discipline
2 sessions · 8 pointsSession 1The paperwork for technical debt management that is actually needed
- Assign responsibility for keeping documentation of technical debt management current.
- Record the technical debt in technical debt management and schedule repayment.
- Confirm that those complying with technical debt management understand why it exists.
- Name a single owner for each element of technical debt management.
Session 2Setting availability and recovery targets for technical debt management honestly
- Anticipate the objections technical debt management will raise and prepare the answers.
- Prepare the summary of technical debt management that senior management will read.
- Restore a backup of technical debt management in a test environment and time it.
- Agree the indicators that will show whether technical debt management is improving.
Technical debt management: incident response and severity
2 sessions · 8 pointsSession 1The change to technical debt management that caused the last outage
- Build the competence framework that supports technical debt management.
- Rank the weaknesses in technical debt management by consequence rather than by ease of fixing.
- Set out the decisions in technical debt management that require sign-off and by whom.
- Measure current load on technical debt management and project it forward twelve months.
Session 2Documenting technical debt management so someone else can operate it
- Check that technical debt management still works when volumes rise unexpectedly.
- Record what was learned when technical debt management did not go as planned.
- Configure alerting on technical debt management that reflects what users experience.
- Remove steps in technical debt management that add effort without adding assurance.
Technical debt management: architecture and designing for failure
2 sessions · 8 pointsSession 1The cost of technical debt management and how to present it
- Set out how exceptions to technical debt management are requested and approved.
- Document the runbook for technical debt management to the level a new engineer could use.
- Apply change control to technical debt management including emergency changes.
- Build the internal briefing that explains technical debt management to those affected.
Session 2Monitoring technical debt management from the user's point of view
- Confirm the support model and escalation path for technical debt management.
- Confirm data retention and deletion rules applied within technical debt management.
- Rehearse the briefing on technical debt management that would follow an incident.
- Assess the exit route from any cloud or vendor dependency in technical debt management.
Technical debt management: requirements, targets and service levels
2 sessions · 8 pointsSession 1Comparing technical debt management with recognised practice
- Run a load test on technical debt management at expected peak plus a margin.
- Inventory third-party dependencies inside technical debt management and their update status.
- Review access rights on technical debt management and remove what is no longer needed.
- State the availability and recovery objectives for technical debt management as numbers.
Session 2Running an incident on technical debt management calmly
- Set delivery and reliability indicators for technical debt management the team trusts.
- Prepare the response for the most likely failure in technical debt management.
- Test the failover for technical debt management rather than assuming it works.
- Define incident severity levels for technical debt management and the response each triggers.
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.