It is very easy to forget to end a Sprint before actual work begins on the next Sprint. Of course, we can get better at manually ending and starting sprints on time; however, how can a Cloud hosted client, cleanup incorrect Sprint end dates?
Can a Sprint automatically end on a given date/time and a new one begin automatically?
Can a completed Sprint's end date be edited after it has been completed?
I've seen this issue asked a couple times, but never is a workaround proposed. I really hope that such an expense, sophisticated system has at least a way to workaround this simple, human error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.