>Projects that don't have deadlines imposed on them, even if they are self-imposed, will take a lot longer than they need to, and may suffer from feature creep and scope bloat.
Another way to say this is;
>Projects that don't have deadlines imposed on them, will take longer, and may benefit from feature advancements and leave you with increased scope with the finished product.
Using words like creep and bloat to describe what is effectively a better solution to a problem is short-sighted and can lead to a false saving, as jobs that are rushed generally need to be re-done at a later date.
1. Project that takes longer has higher chances not to be finished.
2. Feature creep is a thing and it’s a valid concern. In planning you don’t usually do a potential benefit analysis, you do risk analysis, because additional wins are nice to have, yet you are interested in project success more. So focusing on risk rather than benefits here too makes sense.
Another way to say this is;
>Projects that don't have deadlines imposed on them, will take longer, and may benefit from feature advancements and leave you with increased scope with the finished product.
Using words like creep and bloat to describe what is effectively a better solution to a problem is short-sighted and can lead to a false saving, as jobs that are rushed generally need to be re-done at a later date.