It’s the ever-present challenge within projects inclusive of technology: initial development, testing and the “tweaks” along the way, trying to squeeze it all in by the time you cross the line to production.
Too much “tweaking” and you end up with all the unforeseen errors that complicate the launch; too little, and things end up not working and looking like the team ultimately envisioned—but where to draw the line?
The use of freezes along the way can help, but more importantly, especially in today’s ever-automated landscape, is the art of communication, that 1:1, 15 minute check-in with your stakeholders to get perspective that might not otherwise be shared in the context of a team setting? Gold.
...project methodology has shifted over the years from a traditional, more "tortoise" approach of waterfall system development to the more rapid "hare" approach of agile development. The ground you want to stake out for your project is between these two extremes.