Sub-Project vs seperate projects

[MBMRED]

Hi all,

Our organization has been on SPM for about 9 months now.

We have situations where we need 2 projects (with different PMs) from the same demand and the projects are related but independent of one another. We're discussing sub-projects vs creating 2 separate projects.

It's not readily apparent how sub-projects interact with parent project.  Are there any issues or pitfalls we need to be aware of before we start utilizing sub-projects?

Our other thought is to utilize programs to manage these situations, however a program seems like overkill to relate two projects together.

Any feedback is appreciated.

Thank you,

Mathew.

[Mark Manders]

You are currently on 2, but could it ever become more? Programs would be a good way to manage this, because of the relation between the projects (working on the same demand). 

It depends a bit on how you define 'sub project', because to each other, they aren't sub projects (they are related, but not depending). They are sub projects to the demand/program, but because there is no dependency, it should be separate projects, without a relation to each other.
Because both are related to achieve the same goal, you need to have a clear overview of what they are doing and this is where the program comes in.

example: if the demand is to deliver a new office campus and housing for employees and the offices and housing are the separate projects, you want to make sure that sewerage and infrastructure are coming together, so there is an overlap somewhere between the projects where they need to collaborate.

[JLeslie]

What is defined in the scope of the demand, and I would need to understand how are they related but independent?   Deliverables, scope, budget, timeline? My next question would be - are the PMs really different project managers or are they different resources on the same project.    In my mind and I am not saying I am correct, but I would think of building a house. The scope is a complete house.  First the foundation, then the walls, etc.?   It is one project with a singular WBS, but different resources, i.e. the foundation team, framing crew, plumbers etc.  Single deliverable, scope, budget and timeline.  

Also, here is a reference article that may help on the differences of Programs vs Sub Projects- Programs vs. Sub Projects - ServiceNow Community

[MBMRED]

J,

Thank you for your reply. I appreciate the information and the link. 

We are a healthcare org and have 2 teams: A PM-lead IS Facilities team that focuses on the physical IT infrastructure of construction projects and works closely with the construction PMs.  The second team is our EMR team that needs to configure the new location(s) in our EMR.  The EMR project "lives" within the overall IS Facility project as far as timeline goes, but is managed independently from the IS facility project.

Most of the time, this is a one-demand, two-project scenario, and while I agree that the Program is designed to manage & control multiple-related efforts, the PM teams are leaning toward project/sub-project.

Our implementation partner warned us away from project/sub-project and we're not sure why.  Are there any specifics in how they relate that we should be aware of? For example, I know closing the parent will also close the sub.  Can you think of anything else?

Thanks again for the response. I appreciate your thoughts.

Mathew.

[MBMRED]

Mark,

Thank you for the response.

Programs are a solution that's on the table, however the PMs are leaning toward the Project/Sub-project workflow. 

Do you know if there's anything we should be aware of when managing sub-projects within a project?  I know if you close the project, it will also close the sub.  Is there other behavior we should know about?

I'm asking this because our implementation partner warned us off sub-projects early in our standup and we aren't clear on why.

Thanks again. I appreciate your thoughts.