That 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 s

That 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.