Managing Project Dependencies

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with - or even disagree with - leave a comment.

About this Blog

RSS

View Posts By:

Cameron McGaughy
Marian Haus
Lynda Bourne
Lung-Hung Chou
Bernadine Douglas
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Roberto Toledo
Cecilia Wong
Vivek Prakash
Cyndee Miller
Shobhna Raghupathy

Recent Posts

It All Starts With Strategic Clarity, Say Symposium Speakers

Symposium Experts Offer Tips for Winning the Talent War

Organizational Strategic Alignment in Action

PMO of the Year Award Winner Helps Drive Rapid Growth

Influence Without Authority

Email Notifications off: Turn on


Projects don't run in silos or in a vacuum. They run in organized, chaotic environments where everyone is working toward the end result. There's nothing wrong with that--it's how organizations achieve multiple results in a short period of time.

The key, of course, is to manage all these changes and interdependent projects.

But what if you are part of a project that's not a part of any program or portfolio with an assigned program or portfolio manager or director? How do you manage those interdependencies that are not part of your scope?

In my view, it's a matter of paying attention and linking yourself to three key areas:

•    Organization: Culture, processes, standards, rules, events, special blackout periods, etc.

•    Operations: Operational teams responsible for change management, incident management, delivery and quality management/control

•    Project Delivery: Such as a project management office or a business committee or unit that's responsible for project delivery

No matter what dependencies may exist, they will be manifested through these three main channels.
Posted by Dmitri Ivanenko PMP ITIL on: August 20, 2009 02:56 PM | Permalink

Comments

tomas b.
Generally, I would consider two things the biggest threat to such an "orphaned" project.

The first one is a change in company's priorities. That is partially covered in the "organization" area you mention in your post, but basically there is a strong need for enhanced and properly executed stakeholder analysis/management.

The second one—and that one i can not find within your three areas—is resourcing. scheduling conflicts, shifts cased by other project's delays and so on that will definitely occur and without very strict rules of resource allocation and management. The failure of the projects is then inevitable ...

PM Hut
Dmitri,

I believe part of what you're saying falls on the PMO's shoulder, and not only the PMs.

Having said that, I have published an elaborate article on the subject: tips for breaking project dependencies http://www.pmhut.com/tips-for-breaking-project-dependencies. I know for a fact that most project dependencies cannot be broken, but the article offers a different perspective on the subject.

Please Login/Register to leave a comment.

ADVERTISEMENTS

"I'll do the stupid thing first and then you shy people follow..."

- Frank Zappa

ADVERTISEMENT

Sponsors

>