Difference between revisions of "Smooth Succession"
Jump to navigation
Jump to search
BobJonkman (talk | contribs) m (Fixed category...) |
BobJonkman (talk | contribs) m |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== [[Smooth Succession]] === | === [[Smooth Succession]] === | ||
| − | ; Monday, 19 September 2016 | + | ; Date: Monday, 19 September 2016 |
| − | + | ; Event Announcement: http://www.meetup.com/NetSquared-Kitchener-Waterloo/events/232556568/ | |
Sooner or later, people move on. Sometimes they leave for greener pastures and sometimes they just leave. Sysadmins tend to have a lot knowledge about the systems they work with, and often their knowledge is in their heads and their heads alone. As responsible sysadmins, how do we transition out of our jobs without our organizations collapsing behind us? How do our replacements learn the institutional knowledge they need to keep things running? What best practices can we implement to document and share knowledge so that others know what is going on when we are hit by buses? | Sooner or later, people move on. Sometimes they leave for greener pastures and sometimes they just leave. Sysadmins tend to have a lot knowledge about the systems they work with, and often their knowledge is in their heads and their heads alone. As responsible sysadmins, how do we transition out of our jobs without our organizations collapsing behind us? How do our replacements learn the institutional knowledge they need to keep things running? What best practices can we implement to document and share knowledge so that others know what is going on when we are hit by buses? | ||
| + | |||
| + | |||
| + | * [[Smooth Succession/Meeting Notes for 2016-09-19]] | ||
[[Category:NPSA]] | [[Category:NPSA]] | ||
[[Category:Events]] | [[Category:Events]] | ||
Latest revision as of 02:11, 16 October 2017
Smooth Succession
- Date
- Monday, 19 September 2016
- Event Announcement
- http://www.meetup.com/NetSquared-Kitchener-Waterloo/events/232556568/
Sooner or later, people move on. Sometimes they leave for greener pastures and sometimes they just leave. Sysadmins tend to have a lot knowledge about the systems they work with, and often their knowledge is in their heads and their heads alone. As responsible sysadmins, how do we transition out of our jobs without our organizations collapsing behind us? How do our replacements learn the institutional knowledge they need to keep things running? What best practices can we implement to document and share knowledge so that others know what is going on when we are hit by buses?
