3 ms·
I'm presuming in this ideal land, the stories are already ordered in the most optimal way. So no scheduling conflict. Resource and release conflicts don't appe
by UK-Al05 6y ago
I'm presuming in this ideal land, the stories are already ordered in the most optimal way. So no scheduling conflict.
Resource and release conflicts don't appear if you have the right infrastructure.
- choeger 6y agoAre you serious? The "right" infrastructure? Are you limiting your view to a single service, running on a big cluster? Because even then there are permanent conflicts in the persistence layer and resource conflicts express themselves in huge infrastructure bills. But things get really messy when your software is distributed in heterogeneous environments. Say you ship a database yourselves. Or a multi-platform app, or a game, or the control software for medical devices, or... Software development is not just running the next SaaS product.
- UK-Al05 6y agoGive me some concrete examples. Higher infrastructure bills for spinning up new hardware is often cheaper than fixing resource conflicts