There are ways to deliver on time & budget but most developers are not going to like it neither are their "clients". Use the frameworks exactly as they are int

There are ways to deliver on time & budget but most developers are not going to like it neither are their "clients". Use the frameworks exactly as they are intended, don't try to invent new solutions that aren't native to the framework. Anything that takes you outside the beaten path in development is going to be a potentially infinite black box. In other words, a lot of software engineering can't be put in timeboxes because it's actually R&D more than it's development and where each little step forward can add a potentially infinite amount of new tasks to be done or problems to be solved. Add to that the constant need to update, upgrade, improve, re-design and you know it's just not doable. So the primary problem IMO is that we think about a lot of development as if it's something that can be put in boxes. Some can of course and the better and more solid the team becomes to better they are but the teams who struggle are mostly struggling because the expectations for what they are actually doing (inventing problem-solving) isn't matching up with what they are being paid to do (build)