4 ms·
Even your pragmatic issues have a strong cultural component. There are quite a few important projects that on my team that we could afford to have take 20% long
by hn_go_brrrrr 5y ago
Even your pragmatic issues have a strong cultural component. There are quite a few important projects that on my team that we could afford to have take 20% longer. It's more important they have a good result than they arrive as soon as possible. We also have some projects we need done ASAP, which would naturally fall to a full-timer.
- twblalock 5y agoSo, it makes sense to hire part-time people when the timelines can slip and they aren't on the critical path? That's not a very good sales pitch.
- hn_go_brrrrr 5y agoI'm getting downvoted, but I really don't see the problem? Not all of our projects even have a timeline to slip.
- wpietri 5y agoI can believe they don't have explicit timelines. But I'd bet there are implicit ones. Or are you saying that if you just never do them, nobody will notice?
- wpietri 5y agoThat could be a cultural component. But from what I've seen, more often it's a business component. Software features should have a high ROI. The later you put something in production, the lower the return and the higher the investment. Further, the longer a team's cycle time is, the harder it is for the organization to learn. And even for issues that are "cultural", I think one needs particular strategies for managing them. Stakeholders for the important projects that are being delayed will generally not be excited about that. And given that most companies have competitors, those stakeholders might have legitimate reason to want things to go 25% faster. So I'd be curious to see what strategies people have for solving the cultural problems.