Predecessor Status for Projects within Programs

Within projects, functionality exists to make tasks and subtasks dependent on completion of other tasks. This allows projects to move forward in the optimal order and timeframe.

What about allowing the same type of dependencies to exist for Programs?

As a project manager, I often work on multiple projects within an overarching Program (which itself exists within a Portfolio.) There may be multiple projects within a portfolio which depend on one another in order to move forward.  Currently, there is no logical connector between the health or completion of a project and starting another project.

Example Program:  Spring Campaign. 

Below are examples of projects which might exist within the Program.  These are not in order, but there IS an order to them.

Project: Campaign Strategy

Project: Content Strategy

Project: Approved Marketing Copy

Project: Photoshoot

Project: Video Shoot

Project: Social Ads

Project: Web Banners

Project: Campaign Web Pages

Project: Pitch Deck

Project: Sales Enablement Materials

Project: Partner Versioning

Project: Localization Across Regions

Creating functionality which allows dependencies between Projects in a Program has the potential to elevate the interconnected nature of all of the work required to accomplish a project to a level which allows visualization across stakeholders. The visualization could be a game changer in articulation of what is possible given resources, budget, and timeline to accomplish a large multi-faceted goal. The implications for conveying reality to Executive Level Stakeholders allows the vision to be seen in the light of reality. Accountability is underscored by the clear understanding of ALL that is involved.  Silos are removed.