In a project takeover, a project, e.g. the maintenance of a website, is taken over by a new service provider from an old service provider, so that the project responsibility and work is completely transferred to the new service provider. Agencies usually act as service providers. A project takeover can be very complex, so there should be detailed documentation for the project handover.
In the website example, the new agency should be able to understand the project scope, previous developments and future plans. Especially for development, compliance with coding standards and detailed code documentation is an important support for the new developers.
Further information that makes it easier to take on a project:
-
A list of stakeholders, their roles and areas of responsibility
-
List of current or potential risks
-
Project plan or fact sheet, consisting of resources, time, goals, communication channels, etc.
The new service provider should use these documents and information in discussions with stakeholders to find out whether and to what extent they were dissatisfied with the previous service provider and adapt the plan documentation accordingly.
Read about the 6 simple steps a change of agency should go through.
Find out how successful communication with an agency can take place: " Dictionary for communication with agencies".
Further information:
https://www.iapm.net/de/events/iapm-blog/!/show/271/organization-of-a-project-takeover/
Video:
