Difference between revisions of "KWNPSA Upcoming Events"

From SOBAC Wiki
Jump to navigation Jump to search
m (Added subtitle for event)
m (Reformat layout)
Line 1: Line 1:
 
Upcoming meetings of the Non-Profit System Administrator's group:
 
Upcoming meetings of the Non-Profit System Administrator's group:
  
=== Monday, 19 September 2016 ===
+
=== Smooth Succession ===
 
http://www.meetup.com/NetSquared-Kitchener-Waterloo/events/232556568/
 
http://www.meetup.com/NetSquared-Kitchener-Waterloo/events/232556568/
==== Smooth Succession ====
+
; Monday, 19 September 2016
  
 
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?
 
 
  
 
[[Category:NPSA]]
 
[[Category:NPSA]]
 
[[Category:Events]]
 
[[Category:Events]]

Revision as of 21:09, 15 August 2016

Upcoming meetings of the Non-Profit System Administrator's group:

Smooth Succession

http://www.meetup.com/NetSquared-Kitchener-Waterloo/events/232556568/

Monday, 19 September 2016

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?