Q
Problem solve Get help with specific problems with your technologies, process and projects.

Handling project management issues for a proprietary ownership conflict

Project management issues are common but some are worse than others. When a system configuration team refuses to hand over code find out if there's anything the project manager can do to resolve the issue.

You are a project manager on an on-going project. Your company just merged with a large, high profile corporation. Since the merger, the systems configuration team has refused to turn over code for the project because they believe it to be a conflict of proprietary ownership. The project has not been "killed" or gone through change management for restructuring. What are the sequential actions that should be taken to expedite the resolution of this issue?
I'd like to know more about the conflict. I am certainly not a lawyer but I would have hoped that consultants or other internal players on the project evaluated this risk from the beginning. If there are legitimate legal issues, then I would recommend a mediator or arbitrator over a lawsuit. If nothing else, those options will allow for a quicker resolution.
This was last published in October 2009

Dig Deeper on Data management tutorials

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchBusinessAnalytics

SearchAWS

SearchContentManagement

SearchOracle

SearchSAP

SearchSQLServer

Close