Timeboxing in Scrum
The concept of timeboxing in Scrum is a critical factor for success. Without any timeboxing we quickly end up with inefficient development process, too much overhead and very low velocity. From day one it is therefore important to use the time boxing in Scrum as an effective tool to keep the teams velocity as high as possible.
The following table shows the most used timeboxing values used in Scrum:
| Meeting | Timeboxed to |
| Daily scrum | 15 min |
| Sprint planning | 1 hr. initial + 1 hr per sprint week |
| Backlog grooming | 1 hr. |
| Sprint review | No timeboxing |
| Sprint retrospective | 1 hr |
I do not use any general timeboxing from the sprint review as this varies too much from sprint to sprint, and from project to project. In addition the value of the review meeting is strongly related to the amount of discussions, and they should therefore not bee timeboxed without considering the current sprint.
The values used here are from my experience the most efficient, leave some feedback if you think they are wrong