What effects has working in rotating shifts on programming teams?
Posted
by eKek0
on Stack Overflow
See other posts from Stack Overflow
or by eKek0
Published on 2010-02-02T03:06:30Z
Indexed on
2010/03/21
14:01 UTC
Read the original article
Hit count: 283
team
|Productivity
I work in a bank, and the boss now want's that we, the programming team, work on rotating shifts. He wants that sometimes we work from 7am to 3pm, and sometimes on 11.30am to 7.30pm.
He says that we will be more productive working this way, because he has worked with teams just like that and he just knows that. Nobody of the team wants this change, but we don't know how to effectively reject this new rule. I was trying to find some empirical (or almost) evidence about how rotating shifts affects performance of programming teams, and I couldn't. I had read something about rotating shifts, but not exactly about the effect of this on programming teams.
Do you know any research about rotating shifts on programming teams? Did you have any experience with this kind of work?
EDIT: Other teams of the company, like the database administrators team, the help desk team, the communication team or the network administrators team are already working in rotating shifts, and they don't like this but they do it anyway. I think the boss want that we work on rotating shifts too because of them, but since only we do programming I think the effects of rotating shifts could be, at least, different for us.
© Stack Overflow or respective owner