Optimal team sizes for chip projects
What's the optimal team size for a given IC design project? It's a question I hear often from engineering managers and senior executives. What they're actually asking is whether they're over-staffing projects and therefore wasting resources. Implicitly, they're also asking "what's the fewest number of engineers I can put on a given project and still finish on time?" They're important questions directly impacting R&D ROI.
Projects demand a threshold number of engineers to meet schedule targets. Yet, there's a point at which adding resources yields little, if any, additional development throughput—
the exception is when a project desperately needs a particular kind of expertise or specialist. Although most R&D organizations lack the infrastructure to reliably quantify the number of engineers a project needs (which is why many miss schedule), managers instinctively know there is a point of diminishing return. Additional staffing increases overhead, including communication, coordination and consensus-building. That bleeds development time, lowering average productivity among team members. Each additional resource reduces team productivity—throughput increases, but the issue is by how much?
To read the full article, click here
Related Semiconductor IP
- General use, integer-N 4GHz Hybrid Phase Locked Loop on TSMC 28HPC
- JPEG XL Encoder
- LPDDR6/5X/5 PHY V2 - Intel 18A-P
- ML-KEM Key Encapsulation & ML-DSA Digital Signature Engine
- MIPI SoundWire I3S Peripheral IP
Related Blogs
- Synopsys and Intel Team Up on the First UCIe-Connected Chiplet-Based Test Chip
- SLM Solutions for Mission-Critical Aerospace and Government Chip Designs
- Maximizing the Usability of Your Chip Development: Design with Flexibility for the Future
- Morgan State University (MSU) Leveraging Intel 16 and the Cadence Tool Flow for Academic Chip Tapeout