Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
I'm starting to work on the project transition plan. Most of my search results for templates or plans are pretty specific to IT. My project included a much broader scope than just IT.
So far, I have to look at transitioning the following items back to the organization:
That's the easy part. I can build the list of transition items from existing artifacts.
Where I am struggling is the information I should capture for each transition item. So far I have the following attributes:
Project Owner
Business Owner
Transition Date
Transition Actions
The last attribute is meant to capture the steps involved in transitioning the item from the project owner to the business owner.
What else should I consider? I thought of a transition status (i.e., started, in progress, ...) but figured it may be implicit in my transition date and transition plan.
Once I've got something that's fairly reasonable, I'll submit the template to share with the community. Thank you all for your help. Saving Changes...
Sort By:
Paul AzanorProject Consultant| Lagos NigeriaIkoyi, Lagos, Nigeria
Looks like they call it disposition plan. It gave me a few additional ideas for transition items. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
I guess the dispostion plan is a particular case of transition plan. The difference is that the transition is not to someone else but to noghting. Saving Changes...
I recently supported a transition effort from a production environment to the product support team. In addition to transferring the functions themselves here are a couple other items required to execute the functions:
Supporting data- Specifications, test data, and anything else needed to define the product so that the new team had a full configuration definition, and the background information to evaluate problems or proposed changes. This could be digital files, boxes of notebooks, physical test articles, or whatever the receiving organization would need to house somewhere if not in a shared system.
Unique processes and tools: Some functions developed their own applications which might be on a specific PC, or their own methods developed specifically for their function.
Knowledge transfer - In some cases there might be training required for unique processes, or tools. Prior to handing over the work, the receiving org. needs a knowledge transfer plan so they are ready to perform the function. Saving Changes...
Is it a 'one and done' cutover, or will there be milestones? How will you measure 1) progress, and 2) whether the transition is effective or successful? Saving Changes...
Community Champion
