Managing obsolescence
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
track end-of-life risk so upgrades are planned, not forced.
Planned topics
- Inventory every runtime, framework, datastore, and managed service with its version and end-of-support date.
- Vendor viability counts: funding, licence changes, and community health. Verify dates before use.
- Plan upgrades on a calendar, with effort and ownership, ahead of the deadline.
- Security emergencies are the price of a missed calendar.
Draft outline details
Demonstration
an obsolescence calendar table: component, current version, end of support (verify before recording), owner, planned upgrade quarter, effort, risk if missed.
Check your understanding
Why plan upgrades before end of support rather than at it?
Show answer
Late upgrades become emergencies with no time to test or negotiate extended support.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.