Venture Capital Group Acknowledges Overtime Detrimental to Scrum
Jeff was shown a “Maxwell Curve” which depicted that when the team put in more than 40 hours then the velocity of the team went down. According to OpenView Venture Partners, as venture capitalists they always wanted people to work harder than 40 hours a week to double productivity, however now with Scrum the situation is different. According to them,
Now it is different with Scrum. In order to double our productivity we need to work less, certainly no more than 40 hours a week. Scrum is intense and you cannot work extra hours at that pace without losing productivity.
In a similar study, Clinton Keith noted the effect of longer hours on team velocity. According to him if instead of a normal 40 hour week the team was asked to work 60 hours week then the velocity tapered off after the first couple of weeks. Though, in the first couple of weeks under crunch mode the velocity was greater than that of 40 hour weeks, gradually it started to fall and eventually a 60 hour week produced less velocity than the 40 hour week.
On the flip side, Clinton does caution that people sometimes take a flawed interpretation of sustainable pace. Some teams drop parts of their sprint goals if they are faced with too much to do in a 40 hour week. According to him, sustainable pace should not be an escape route for teams to drop committed sprint goals. Once commitments have been made, teams should strive hard to meet them and constantly look for small improvements during the course of the sprint which would allow them to utilize time more effectively. A 1% improvement per sprint would allow make significant impact in the long run.
According to him working more than the sustainable pace once a while is not harmful, however it should not become practice.
If it's the last Sprint before a major release we'll see teams putting in a couple of weeks of late nights and rarely a weekend. If they find that they are doing this too often, they need to improve how they estimate.
Thus, sustainable pace does allow teams to be more productive given that it is cautiously used, not abused.
Kevin E. Schlabach
Delivering Performance Under Schedule and Resource Pressure: Lessons Learned at Google and Microsoft
Ivan Filho Mar 06, 2014