seniorboop
Active Member
- Jun 5, 2021
- 753
- 2,299
- 321
We figured this out in professional development quite awhile ago, giving release dates further out then you believe you need is exactly what you do if it's not a product that is compatible with sprinting. Honestly, you don't even need to be a developer; anyone that has a project-oriented career knows how these things go.I have little doubt DB thought it quite likely each time they'd meet the release date. Giving a release date further in the future than you think is necessary has its own problems. What if you finish early? Do you release and then people expect it early next time, or sit on the release until the date arrives while people speculate on whether it will happen?
If you finish early? Chances are you still haven't caught all bugs or something looks off in a few scenes. Use the bonus time to fix.
Finished early and you believe the update is in a polished and ready state? Start working on the next update in the meantime.
The loss of goodwill in relenting on your word continuously does almost irreparable damage to your credibility and you can see it in this thread, in which people are commenting to come back in a week because every missed release has panned out to almost exactly that. It's better to be ready to go by a further out release date than it is to fail to deliver on a date you've committed to with an announcement.
It's demoralizing for the fans and it's demoralizing for the developer(s) who have to face the music. Go easy mode and just abandon release dates or go professional mode and give yourself an appropriate amount of time. This isn't a shot at the dev, just general development 101.