For the time being, we have a large offshore development team that mostly takes instructions from the California team. It’s like having team members that can do 30 hours of work per day. I’m trying to schedule Sprint Review, Retrospective, and Planning. Because India is a half-day ahead of us, I feel compelled to narrow the gap between Review/Retrospective and Planning, so that offshore doesn’t have an unplanned day to start every sprint.
So, question: are there any hard-and-fasts you go by on the sequencing of these meetings? For instance, Sprint N+1 Planning the day before Sprint N Demo/Retro would fix my problem, but is probably a bad idea. And having Demo, Retro, and a Planning all on the same day is exhausting. But I have to compromise on something. Your recommendation?