Im particularly interested in how people are supposed to put in resources that work across multiple programs or portfolios or who dont work at the requirement level but who work on tasks that are at a program or portfolio level. i.e. do you track a task in a dummy requirement level for activities like General Meetings, Project Management or Architecture Review etc (if working in waterfall methodology?) or do you reduce your number of hours per project to only include pure test/dev effort and have everything else tracked outside Spiraplan/Spirateam? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/best-practices/2915.aspxthreadId=2915Madeleine Lowe (madeleinelowe@westfieldspecialty.com) Im particularly interested in how people are supposed to put in resources that work across multiple programs or portfolios or who dont work at the requirement level but who work on tasks that are at a program or portfolio level. i.e. do you track a task in a dummy requirement level for activities like General Meetings, Project Management or Architecture Review etc (if working in waterfall methodology?) or do you reduce your number of hours per project to only include pure test/dev effort and have everything else tracked outside Spiraplan/Spirateam? Tue, 30 Apr 2024 16:11:57 -04002026-05-07T11:32:26-04:00/Support/Forum/spirateam/best-practices/2915.aspxmessageId=7642Victoria D (nino.diasamidze@inflectra.com) Hello, To effectively manage resources working across multiple programs or portfolios in Spira, three-tiered approach looks convenient: 1. Use the Program/Portfolio Resources View: Instead of looking at resource availability within a single project, navigate to the Program or Portfolio level. In the Planning > Resources section, Spira aggregates a users total workload across all projects they are assigned to. This is the only way to see if a developer is 100% allocated in Project A while simultaneously having 50% allocation in Project B. 2. Define Project-Specific Work Hours: In each product, you can define how many hours per week a user is dedicated to that specific project . For example, if a Lead Architect works across 4 projects, you might set them to 10 hours/week in each. Spiras capacity engine will then show them as Over-allocated if their total tasks exceed those specific bounds. 3. Create an Overhead/Admin Project for Non-Project Work: For resources that dont work 100% on specific deliverables (e.g., Management, Architecture, or General Support), it is a best practice to create a permanent Operational Support project. Assign these users there and create Administrative Requirements or Support Tasks. This ensures their invisible work is accounted for in the overall Portfolio capacity and doesnt appear as free time to the PMO. By centralizing these views at the Portfolio level, you avoid the silo effect where each PM thinks they have the developers full attention. Regards, Victoria - Thu, 07 May 2026 11:32:26 -04002026-05-07T11:32:26-04:00/Support/Forum/spirateam/best-practices/2915.aspx#reply7642