Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
Summary
Our company runs two week sprints for our software development team. We have many projects our team shares with some being individual projects. We've noticed that when we end our sprint an hour or so before our sprint review meeting that we sometimes have problems demoing our software in the sprint review meeting.
Question
What is a good time to stop development before the sprint review meeting? An hour, two hours, a day, etc... What does Agile SCRUM recommend?
Scrum says nothing about this. You should hold the review as soon as practical after the sprint ends. That means after all the work is done, all tests have passed, and the team has had a chance to prepare for the demo.
This is all the scrum guide has to say about the timing of the review:
A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.
Notice that it says nothing about the timing. As with all things related to Agile, your team should decide what works best for your team.
Most of the teams I've worked on found it convenient to finish the sprint at the end of a day, and then use the next day for reviews, retrospectives, and planning the next sprint.
As an aside, it sounds like the real problem isn't in picking a time, it's in choosing a method to demonstrate what you've done that doesn't have dependencies on other teams. You should probably focus on solving that problem instead of trying to pick a new time.
