Project Interdependency – CV tips
As part of the CV Tips series I wanted to address project interdependency, it is an important factor to cover in the CV if you have had exposure to it as there is a big difference in portfolios which have dependencies to ones which are not interlinked. In basic terms Project Interdependency is a term often used where two or more projects relate in particular ways – for example if one of the projects fails to deliver expected results/benefits then all other related projects will be affected somehow. This can be resource conflicts, cost (if there is an overspend and a bunch of projects share this then other projects can fall short of funds), a project may be dependent on another project starting or meeting certain deliverables by milestones. Because of these reasons project interdependency is seen as a major risk to the other affected/related projects – if one project fails, then the rest can all come to a halt or fail also.
Now we have cleared up what a project interdependency is, you can see why this is a great competency to add into the CV if you have been managing/supporting this – the role of a PM always involves a certain level of balancing various teams and groups, ensuring all is being completed and delivered to plan, but when it comes to project interdependency there is a high emphasis on bringing together all parties to ensure success. Although there is the administrative element, there is also the all important governance, relationship building, team leading, negotiating with suppliers and a spectrum of other skills all rolled into one.
I think you will agree the competency is worthy of a bullet point on the CV, again, good examples may warrant being placed in the key achievements and of course you should look to add into the description of the portfolio when talking through volume of projects, programmes, etc.