Things to do when transitioning jobs

Clash Royale CLAN TAG#URR8PPP

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
4
down vote

favorite

2

This is my first time to resign as an IT Application Developer and I will be starting to work with my new employer after the 30 days notice that I gave in my resignation letter.

I'm new to this situation and I need some tips what are the right things to do during job transition so that my current workmates will not get difficulties when I'm gone.

career-development professionalism new-job job-change knowledge-transfer

share|improve this question

edited Sep 7 '12 at 3:21

Rarity

4,37643457

asked Sep 7 '12 at 1:28

BizApps

1265

add a comment | 

up vote
4
down vote

favorite

2

This is my first time to resign as an IT Application Developer and I will be starting to work with my new employer after the 30 days notice that I gave in my resignation letter.

I'm new to this situation and I need some tips what are the right things to do during job transition so that my current workmates will not get difficulties when I'm gone.

career-development professionalism new-job job-change knowledge-transfer

share|improve this question

edited Sep 7 '12 at 3:21

Rarity

4,37643457

asked Sep 7 '12 at 1:28

BizApps

1265

add a comment | 

up vote
4
down vote

favorite

2

up vote
4
down vote

favorite

2

2

This is my first time to resign as an IT Application Developer and I will be starting to work with my new employer after the 30 days notice that I gave in my resignation letter.

I'm new to this situation and I need some tips what are the right things to do during job transition so that my current workmates will not get difficulties when I'm gone.

career-development professionalism new-job job-change knowledge-transfer

share|improve this question

edited Sep 7 '12 at 3:21

Rarity

4,37643457

asked Sep 7 '12 at 1:28

BizApps

1265

This is my first time to resign as an IT Application Developer and I will be starting to work with my new employer after the 30 days notice that I gave in my resignation letter.

I'm new to this situation and I need some tips what are the right things to do during job transition so that my current workmates will not get difficulties when I'm gone.

career-development professionalism new-job job-change knowledge-transfer

share|improve this question

edited Sep 7 '12 at 3:21

Rarity

4,37643457

asked Sep 7 '12 at 1:28

BizApps

1265

share|improve this question

share|improve this question

edited Sep 7 '12 at 3:21

Rarity

4,37643457

edited Sep 7 '12 at 3:21

Rarity

4,37643457

edited Sep 7 '12 at 3:21

Rarity

4,37643457

4,37643457

asked Sep 7 '12 at 1:28

BizApps

1265

asked Sep 7 '12 at 1:28

BizApps

1265

asked Sep 7 '12 at 1:28

BizApps

1265

1265

add a comment | 

add a comment | 

1 Answer
1

active

oldest

votes

up vote
4
down vote



accepted

A good place to start is by documenting your current roles/responsibilities and any information relevant to each one. As an application developer that might not include too much specific information, but if there are any server instances that you manage you might want to consider listing the hostname, login details, configuration info, and similar information for each one.

Similarly, if you're the keeper of any important developer account passwords (or details for any testing accounts, etc.) you should ensure that they are properly documented somewhere and that the accounts are transitioned over to the company if necessary.

If your company has a password protected wiki that would be a good place for storing this information. Though check first in case they already have a policy about where this sort of information should be kept.

You may also want to discuss with your manager and see if they'd like you to set aside some time to help with interviewing and/or training your eventual replacement, or if there's any specific information they want to make sure you document.

share|improve this answer

answered Sep 7 '12 at 1:36

aroth

8,29812646

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  In addition, it would be good to leave some documentation about the work you've done. It is very difficult to read someone else's code. So comments, class diagrams, workflow description would be very useful and appreciated.
  – superM
  Sep 7 '12 at 11:41
  
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "423"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f3765%2fthings-to-do-when-transitioning-jobs%23new-answer', 'question_page');

);

Post as a guest

Name Email

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
4
down vote



accepted

A good place to start is by documenting your current roles/responsibilities and any information relevant to each one. As an application developer that might not include too much specific information, but if there are any server instances that you manage you might want to consider listing the hostname, login details, configuration info, and similar information for each one.

Similarly, if you're the keeper of any important developer account passwords (or details for any testing accounts, etc.) you should ensure that they are properly documented somewhere and that the accounts are transitioned over to the company if necessary.

If your company has a password protected wiki that would be a good place for storing this information. Though check first in case they already have a policy about where this sort of information should be kept.

You may also want to discuss with your manager and see if they'd like you to set aside some time to help with interviewing and/or training your eventual replacement, or if there's any specific information they want to make sure you document.

share|improve this answer

answered Sep 7 '12 at 1:36

aroth

8,29812646

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  In addition, it would be good to leave some documentation about the work you've done. It is very difficult to read someone else's code. So comments, class diagrams, workflow description would be very useful and appreciated.
  – superM
  Sep 7 '12 at 11:41
  
  

  
  
  
  

add a comment | 

up vote
4
down vote



accepted

A good place to start is by documenting your current roles/responsibilities and any information relevant to each one. As an application developer that might not include too much specific information, but if there are any server instances that you manage you might want to consider listing the hostname, login details, configuration info, and similar information for each one.

Similarly, if you're the keeper of any important developer account passwords (or details for any testing accounts, etc.) you should ensure that they are properly documented somewhere and that the accounts are transitioned over to the company if necessary.

If your company has a password protected wiki that would be a good place for storing this information. Though check first in case they already have a policy about where this sort of information should be kept.

You may also want to discuss with your manager and see if they'd like you to set aside some time to help with interviewing and/or training your eventual replacement, or if there's any specific information they want to make sure you document.

share|improve this answer

answered Sep 7 '12 at 1:36

aroth

8,29812646

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  In addition, it would be good to leave some documentation about the work you've done. It is very difficult to read someone else's code. So comments, class diagrams, workflow description would be very useful and appreciated.
  – superM
  Sep 7 '12 at 11:41
  
  

  
  
  
  

add a comment | 

up vote
4
down vote



accepted

up vote
4
down vote



accepted

A good place to start is by documenting your current roles/responsibilities and any information relevant to each one. As an application developer that might not include too much specific information, but if there are any server instances that you manage you might want to consider listing the hostname, login details, configuration info, and similar information for each one.

Similarly, if you're the keeper of any important developer account passwords (or details for any testing accounts, etc.) you should ensure that they are properly documented somewhere and that the accounts are transitioned over to the company if necessary.

If your company has a password protected wiki that would be a good place for storing this information. Though check first in case they already have a policy about where this sort of information should be kept.

You may also want to discuss with your manager and see if they'd like you to set aside some time to help with interviewing and/or training your eventual replacement, or if there's any specific information they want to make sure you document.

share|improve this answer

answered Sep 7 '12 at 1:36

aroth

8,29812646

A good place to start is by documenting your current roles/responsibilities and any information relevant to each one. As an application developer that might not include too much specific information, but if there are any server instances that you manage you might want to consider listing the hostname, login details, configuration info, and similar information for each one.

Similarly, if you're the keeper of any important developer account passwords (or details for any testing accounts, etc.) you should ensure that they are properly documented somewhere and that the accounts are transitioned over to the company if necessary.

If your company has a password protected wiki that would be a good place for storing this information. Though check first in case they already have a policy about where this sort of information should be kept.

You may also want to discuss with your manager and see if they'd like you to set aside some time to help with interviewing and/or training your eventual replacement, or if there's any specific information they want to make sure you document.

share|improve this answer

answered Sep 7 '12 at 1:36

aroth

8,29812646

share|improve this answer

share|improve this answer

answered Sep 7 '12 at 1:36

aroth

8,29812646

answered Sep 7 '12 at 1:36

aroth

8,29812646

answered Sep 7 '12 at 1:36

aroth

8,29812646

8,29812646

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  In addition, it would be good to leave some documentation about the work you've done. It is very difficult to read someone else's code. So comments, class diagrams, workflow description would be very useful and appreciated.
  – superM
  Sep 7 '12 at 11:41
  
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  In addition, it would be good to leave some documentation about the work you've done. It is very difficult to read someone else's code. So comments, class diagrams, workflow description would be very useful and appreciated.
  – superM
  Sep 7 '12 at 11:41
  
  

  
  
  
  

3

3

In addition, it would be good to leave some documentation about the work you've done. It is very difficult to read someone else's code. So comments, class diagrams, workflow description would be very useful and appreciated.
– superM
Sep 7 '12 at 11:41

In addition, it would be good to leave some documentation about the work you've done. It is very difficult to read someone else's code. So comments, class diagrams, workflow description would be very useful and appreciated.
– superM
Sep 7 '12 at 11:41

add a comment | 

 

draft saved

draft discarded

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f3765%2fthings-to-do-when-transitioning-jobs%23new-answer', 'question_page');

);

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Name Email

Name

Email

Name Email

Name

Email