In my experience, many software projects are late because the teams are chronically understaffed. If you are completing deadlines reliably on time, the managers feel that you have too many people on your team, so they remove one or two.
It’s interesting that you say that, because my experience (US, large corporation IT—think large banks, large retail, 100,000+ total employees) has been the exact opposite. The projects that I’ve been working on have been all quite overstaffed, resulting in poor software architecture, thanks to Conway’s Law. When I worked at the major retailer, for example, I genuinely felt that their IT systems would be healthier and projects would delivered more quickly if they simply fired half the programmers and let the other half get on with writing code rather than Slack messages.
It’s interesting that you say that, because my experience (US, large corporation IT—think large banks, large retail, 100,000+ total employees) has been the exact opposite. The projects that I’ve been working on have been all quite overstaffed, resulting in poor software architecture, thanks to Conway’s Law. When I worked at the major retailer, for example, I genuinely felt that their IT systems would be healthier and projects would delivered more quickly if they simply fired half the programmers and let the other half get on with writing code rather than Slack messages.