- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Our team is new to ServiceNow and we could use some guidance on the use of subprojects. We need to capture programs, projects, and subprojects our team supports (another team in our organization manages the portfolio). Currently we are capturing subprojects on the projects tab and adding "SUB PRJ" at the beginning of the project name to help differentiate them from the parent projects. We have not yet started using Resource Management.
- Is functionality for subprojects being deprecated?
- If not, what best practices and gaps should we consider?
Thank you,
Samantha
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi Samantha,
Subprojects are still supported in the current ServiceNow Australia release, so you don't need to avoid them based on deprecation concerns.
A few best practices to consider:
- Use the parent-child relationship: Create a subproject under its parent project instead of relying on the "SUB PRJ" naming prefix to distinguish it.
- Use Programs for grouping related projects: If you need to track a broader initiative containing multiple projects, a Program may be more appropriate than making everything a subproject.
- Define ownership and governance: Since another team manages the portfolio, align with them on who owns the portfolio, programs, parent projects, and subprojects.
- Validate reporting and rollups: Confirm how schedule, progress, cost, and resource requirements roll up to parent projects in your release.
- Consider resource management separately: You can establish the project hierarchy before adopting Resource Management, then validate how resource assignments and capacity planning fit your process.
Manage projects in Project Workspace
https://www.servicenow.com/docs/r/it-business-management/project-workspace/use-projects-pw.html
I'd start with the OOTB hierarchy and avoid custom naming conventions as the primary way to identify subprojects.
Helpful? Please mark the response as Accepted Solution ✅ and close the thread — this helps future readers find the solution faster.
Regards,
Sachinvic
✨ArchX Certified | ✨ 16x ServiceNow AI MVP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi Samantha,
Subprojects are still supported in the current ServiceNow Australia release, so you don't need to avoid them based on deprecation concerns.
A few best practices to consider:
- Use the parent-child relationship: Create a subproject under its parent project instead of relying on the "SUB PRJ" naming prefix to distinguish it.
- Use Programs for grouping related projects: If you need to track a broader initiative containing multiple projects, a Program may be more appropriate than making everything a subproject.
- Define ownership and governance: Since another team manages the portfolio, align with them on who owns the portfolio, programs, parent projects, and subprojects.
- Validate reporting and rollups: Confirm how schedule, progress, cost, and resource requirements roll up to parent projects in your release.
- Consider resource management separately: You can establish the project hierarchy before adopting Resource Management, then validate how resource assignments and capacity planning fit your process.
Manage projects in Project Workspace
https://www.servicenow.com/docs/r/it-business-management/project-workspace/use-projects-pw.html
I'd start with the OOTB hierarchy and avoid custom naming conventions as the primary way to identify subprojects.
Helpful? Please mark the response as Accepted Solution ✅ and close the thread — this helps future readers find the solution faster.
Regards,
Sachinvic
✨ArchX Certified | ✨ 16x ServiceNow AI MVP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you for the information, Sachinvic. Do you anticipate the Subprojects tab going away in a future release?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
You're welcome, Samantha.
I couldn't find a deprecation notice for the Subprojects tab. For confirmation of its future roadmap, ServiceNow would be the authoritative source.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Thank you, I think we have enough information to move forward. Appreciate your help.
Samantha
