{"id":9581,"date":"2021-10-12T15:17:12","date_gmt":"2021-10-12T13:17:12","guid":{"rendered":"http:\/\/axiante.com\/?p=9581"},"modified":"2021-10-12T15:17:14","modified_gmt":"2021-10-12T13:17:14","slug":"how-to-transfer-a-finished-project-to-the-application-maintenance-team","status":"publish","type":"post","link":"http:\/\/axiante.com\/en\/insights\/how-to-transfer-a-finished-project-to-the-application-maintenance-team\/","title":{"rendered":"[How to] Transfer a finished project to the Application Maintenance team"},"content":{"rendered":"\n

It may seem trivial, but starting well is a necessary step to generate value with Application Maintenance. Let\u2019s see how.<\/em>

In our last article dedicated to Application Maintenance we talked about the need for Cios to have innovative and proactive services, in order to adopt an agile approach and a management that ensures continuity.<\/strong>

More than 90% of AM\u2019s efforts are directed to cost containment, performance maintenance and service levels. If on the one hand all this is fully understandable, on the other it is certainly reductive. With technological developments affecting all organizations, Cios have the opportunity to create a wider value even in the perimeters of MA.<\/strong>
<\/p>\n\n\n\n

How?<\/h4>\n\n\n\n

There are different ways to achieve this result, in this deepening we will start from the importance of starting off on the right foot.

Once the application developments are completed, the crucial moment arrives to transfer the project into the hands of those who will be in charge of support and maintenance. In order for the latter to generate value and to be truly proactive and evolutionary, it is necessary to pay particular attention to the setting of this step, which at first glance might seem simple.<\/p>\n\n\n\n

We have prepared this short checklist, so that it can be of support to those who are preparing to face this stage.<\/h4>\n\n\n\n

Don\u2019t wait to get the AM team involved<\/strong>. Simply put, the sooner the better. In this way, all the resources of the support and maintenance team will have valuable time to learn the best technical and functional aspects of the project. Do not wait for the end of development, but make sure that some crucial activities have been carried out for full operation and autonomy:<\/p>\n\n\n\n

Check that the support and maintenance team has clear documentation available<\/strong> so they know exactly what to do. This operational information shall be detailed and ordered, complete and accurate;<\/strong><\/p>\n\n\n\n

Prepare the documentation to be one and centralized<\/strong>, to avoid any confusion and a long and complicated process;<\/p>\n\n\n\n

Create the accounts<\/strong> for the AM team with specific and dedicated permission levels;<\/p>\n\n\n\n

Create test environments or define procedures<\/strong>, in order to allow autonomy<\/p>\n\n\n\n

Get the trial leaders involved. <\/strong>Process managers will be those who will be responsible for transferring the project within their business units and then to their teams. It is important that they are involved from the outset so that they can highlight any discrepancies between functionality and needs.<\/p>\n\n\n\n

Communicating well means being successful<\/strong>: feedback, questions and suggestions must go through specific channels of communication, following procedures agreed and defined previously. This guarantees transparency and order.<\/p>\n\n\n\n

Summing up<\/h4>\n\n\n\n

There are many key details<\/strong> to consider at this stage:<\/p>\n\n\n\n