|
Knowledge Transfer - What to Remember not to Forget |
|
|
Friday, 24 March 2006 |
This week I've been on both the giving and receiving ends of the knowledge transfer process. I'm transitioning out of one company where they've recently "retired" PeopleSoft and the new folks just need to keep it running for historical purposes. And I'm transitioning into another company that needs some help filling a PeopleSoft Administrator position until they can hire someone permanently.
In looking over my notes for the week, I've come up with a list of topics that no PeopleSoft admin/dba knowledge transfer experience should be without. I'm sure most of this list is standard across many technical positions. Hopefully it will give you a place to start as you move up, out, or take over new responsibilities.
- Contact list with roles and responsiblities
- Architecture Diagram for Dev, Test and Production that shows the servers and various PeopleSoft Internet Architecture components
- Server List w/ description/purpose, IP addresses, memory, CPU, and disk capacity
- Database Instances and corresponding PS Environments
- Documentation index - what documentation exists and where it is
- Password lists, including server, application and database accounts
- Customization lists
- Issues list
- Current tasks and projects that the person you're replacing is involved with
- Access to servers, applications
- Remote access software and instructions for using it
- Interface diagram
- Anything that's not maintained within standard PeopleTools like special database triggers or scripts run via cron
- Coding standards with naming conventions
- Time reporting procedures
- Production Change Management procedures
- Migration procedures
Comments () |
 |
|
|
|
 |
|
Last Updated ( Friday, 24 March 2006 )
|
