> While it is true that a narrow set of low value software projects are tamable with a Gantt chart, high value software projects that fill previously unmet need

> While it is true that a narrow set of low value software projects are tamable with a Gantt chart, high value software projects that fill previously unmet needs do not lend themselves to being tamable by predictive scheduling techniques. I think the author vastly overestimates the value and importance of project that most developers work on. I don’t think I’ve ever worked on anything that I could consider “high value”. I’ve worked in big (and small) companies, working on Big Important Projects, but if I’m being realistic I think the overall value and actual importance is actually quite low. Other than that, I think the essay has a fatal misunderstanding - it’s not about setting deadlines, but it’s about estimating what it costs to do build software. This is useful because it helps us guess when it would be done, how much can be delivered, etc.