| Context | A Scrum Team is working overtime during a Sprint. |
| Problem | Working hours are increasing while productivity and quality is decreasing. Development Teams are often driving/driven hard to reach a goal by working overtime (“crunch time”). And if this tactic seems to produce the desired result, it is being done again and again. Driving a team too hard produces errors and burn out. |
| Forces | too little/too much working hours vs. results too little/too planning |
| Solution | Keep a constance pace and avoid deviations External dependencies may lead to “crunch time”, but the cost of increasing working hours has to be paid afterwards because there is a limit to how many hours team members are productive and deliver high-quality results. And above that, people take their problems home which they encountered at work. So problem solving continues outside the office, often on the subconscious level. Working 8 hours a day is a good goal if the productivity during that time is high. Trying to work longer often means distributing the same work throughout a longer timespan. So get the Scrum Team to perform during a fixed timespan each day and limit overtime at all costs. To support the Development Team, it is highly recommended to plan for unexpected complications in advance and product high-quality input for the Development Team. Try to avoid delays and bad planning on the product management level as it backfires during the realization phase. |
| Resulting Context | Velocity, quality and working hours are brought back to normal. |
Dieser Artikel wurde von Andreas Heilwagen am 27.07.2011 um 07:00 gepostet und unter Scrum eingeordnet. Sie können Kommentaren über den RSS 2.0-Feed folgen. Das Posting steht unter der Creative Commons-Lizenz wenn nicht anders vermerkt.
