It seems like the development process is somewhat waterfall-ish (which most development often tends towards). With that in mind, I believe that the original pla

It seems like the development process is somewhat waterfall-ish (which most development often tends towards). With that in mind, I believe that the original plan - of leaving right after the app goes into production had a small flaw in it. In my experience there are often a large set of work that is left when a big production release happens - from the minor like bug fixes and features that were deprioritized to the bigger and often more urgent ones like performance problems and non-validated 'shadow beliefs' being tested. I would recommend sticking with your original plan, but making sure to spend the next week or two to mentally prepare the team that they are likely only just finishing the boring 1/3 of building software and going to start making an impact in the 'real-world'.