Team burnouts occur when multiple or all the members of the team are failing to maintain work expectations. Have you forgotten to keep a buffer in the time estimate? In his blog article, John Goodpasture talks about 5 facts about team burnouts you have not noticed before.
Reasons Behind Team Burnouts
It is not possible to issue a week’s holiday to address and heal team burnouts. Those resources cost the company money. So, Google and Microsoft give time-offs where the team members can refresh their focus through self-improvement. Following are the 5 facts about team burnouts you have not noticed before:
- Pushing Productivity Limit: Agile leader Scott Ambler opined that productivity decreases after you hit 70 percent of your team capacity. Just before the descent starts, the team would be seen performing close to its expected output benchmark.
- Brooks’ Prediction: Fred Brooks observed that adding more resources to a project that has overshot its deadline delays it further. People call this phenomenon Brooks’ Law, named after the IBM-370 project leader.
- Applying Physics: In the wave theory, if a load cannot absorb an applied energy, it simply reflects it. If you force teams to work beyond their capacity, it is going to cause team burnouts. That is a reflection of the extra work-load your team is carrying.
- Limiting WIPs: To avoid team burnouts, the easy solution from sponsors would be to add more resources. Never helps. Know when to limit WIPs because teams cannot work on multiple things parallelly without comprising on the quality of all.
- Daniel Pink’s Iteration Methods: Daniel Pink advises that you should let the team work on project issues for 1 week after every six 2-week iterations. Read “Drive: The Surprising Truth About What Motivates Us” to understand his method.
To view the original article in full, visit the following link: http://www.johngoodpasture.com/2019/02/burning-up-team.html