Wednesday
Jul282010
Drawback that you might not aware in crashing your schedule
Wednesday, July 28, 2010 at 1:19AM
Typical scenario - you have a handful of features but your team can only finish part of them, now you want them to work overtime to do them all.
We all have this desire and probably have experienced this. You should have heard about the different draw back, like decline in quality, and a drop in morale. But there's one thing you might not aware.
Upon finishing your tasks, your team will get through a period of procrastination.
Why? They are paying the debt that have loan, just like the oxygen debt that build up through exercise. Your team will feel they have already done a lot and "deserved" to laid back a bit, to regain the momentum before marching forward for the new tasks. And this is the problem, the laid back usually drags on, and even when they can ramp up to move forward, they need time to get back to the momentum.
Thus, try to avoid the temptation to sprint. Keep the pace that your team that feels comfortable, and you can get a more consistent focus factor for each iteration.
We all have this desire and probably have experienced this. You should have heard about the different draw back, like decline in quality, and a drop in morale. But there's one thing you might not aware.
Upon finishing your tasks, your team will get through a period of procrastination.
Why? They are paying the debt that have loan, just like the oxygen debt that build up through exercise. Your team will feel they have already done a lot and "deserved" to laid back a bit, to regain the momentum before marching forward for the new tasks. And this is the problem, the laid back usually drags on, and even when they can ramp up to move forward, they need time to get back to the momentum.
Thus, try to avoid the temptation to sprint. Keep the pace that your team that feels comfortable, and you can get a more consistent focus factor for each iteration.
Reader Comments