Leave a record of what you have done, so the project will not miss you if you leave.


         If change is the only constant, then resources on a project  will change. The risk in such change is that a person’s contribution to a project will be lost, and that the new person assigned to the project will have to start over.


        This is a particular risk in “quick and dirty” projects  where an operating result is produced, but no one else can understand the code that was produced. However, if the contribution involves producing quality artifacts in my previous post, there is always a point-in-time record of what has been accomplished so far, which can be used by new project resources to continue the project with minimal disruption.

Would you recommend this article?

Thanks for taking the time to let us know what you think of this article!
We'd love to hear your opinion about this or any other story you read in our publication. Click this link to send me a note →

Jim Love, Chief Content Officer, IT World Canada
Previous articleToronto SAM Summit on June 16, 2011
Next articleThe Tipping Point of Postal Strikes