Project Management

Please login or join to subscribe to this thread

How to mitigate the risk if completion of project (with big technical debt and least documentation) is dependent on domain holders only?

linkedin twitter facebook   Information Technology  
avatar
Amir Ali Project Manager| Northbay Solutions Pvt Ltd Lahore, Punjab, Pakistan
Consider a situation where a project was not well executed by a project manager and it is handed over to another project manager in a bad situation. It has huge technical debt and least documentation. There are domain holders staying since long time and they can complete the project successfully.

Now, risk is that replacing domain holders would add impact on cost and schedule. If domain holders leave before documentation or adding replacements then project will most likely be failed.

What are the recommendations in this situation?
Sort By:
avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Amir, correctly document any new risks and assumptions, and manage stakeholder expectations of these.
...
1 reply by Amir Ali
Apr 02, 2018 12:46 PM
Amir Ali
...
Thanks Sante.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
The only thing you can do is create a knowledge management environment. In the minetime, each time you have to start a new initiative in this environment make the risk visible and publish the risk according the audience. Some people will pay attention is you put them into monetary values, some other put attention if you put them into other type of value. The first people you have to demonstrate is in danger is the people that have the knowledge into their heads. I understand you because I was in this type of situations including few time ago.
...
1 reply by Amir Ali
Apr 02, 2018 12:45 PM
Amir Ali
...
Thanks Sergio.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Amir -

In addition to managing the risks of the loss of this knowledge, you might need to assess and get approval on a change request to explicitly capture this knowledge. If your leadership refuses to pay for the costs of doing this, they will be accepting the risk of knowledge loss.

As far as the technical debt goes, there are two choices - pay me now or pay me later. You can make the case for working down the debt within the project, but if there is a hard deadline or cost constraint, it might have to be pushed to future projects to do so.

Kiron
...
1 reply by Amir Ali
Apr 02, 2018 12:47 PM
Amir Ali
...
Thanks Kiron. I liked the idea of treating knowledge transfer and technical debt separately although there is a collective challenge.
avatar
Amir Ali Project Manager| Northbay Solutions Pvt Ltd Lahore, Punjab, Pakistan
Apr 01, 2018 7:35 PM
Replying to Sergio Luis Conte
...
The only thing you can do is create a knowledge management environment. In the minetime, each time you have to start a new initiative in this environment make the risk visible and publish the risk according the audience. Some people will pay attention is you put them into monetary values, some other put attention if you put them into other type of value. The first people you have to demonstrate is in danger is the people that have the knowledge into their heads. I understand you because I was in this type of situations including few time ago.
Thanks Sergio.
avatar
Amir Ali Project Manager| Northbay Solutions Pvt Ltd Lahore, Punjab, Pakistan
Apr 01, 2018 6:14 PM
Replying to Sante Delle-Vergini, PhD
...
Amir, correctly document any new risks and assumptions, and manage stakeholder expectations of these.
Thanks Sante.
avatar
Amir Ali Project Manager| Northbay Solutions Pvt Ltd Lahore, Punjab, Pakistan
Apr 02, 2018 8:20 AM
Replying to Kiron Bondale
...
Amir -

In addition to managing the risks of the loss of this knowledge, you might need to assess and get approval on a change request to explicitly capture this knowledge. If your leadership refuses to pay for the costs of doing this, they will be accepting the risk of knowledge loss.

As far as the technical debt goes, there are two choices - pay me now or pay me later. You can make the case for working down the debt within the project, but if there is a hard deadline or cost constraint, it might have to be pushed to future projects to do so.

Kiron
Thanks Kiron. I liked the idea of treating knowledge transfer and technical debt separately although there is a collective challenge.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Seriousness is the only refuge of the shallow."

- Oscar Wilde

ADVERTISEMENT

Sponsors