productivity - What effects has working in rotating shifts on programming teams? -


I work in a bank, and the boss now wants that we, the programming team, work on rotating changes . She wants that we sometimes work from 7 a.m. to 3 p.m. and sometimes work from 11.30 hrs to 7.30 hrs.

He says that we will do more useful things in this way, because he has worked with teams, Em> he just knows that anybody in the team wants to make this change, But we do not know how to reject this new rule effectively. I was trying to find out some empirical (or nearly) proofs of how the ongoing changes influenced the performance of the programming teams and I could not. I had read something about revising the changes, but not at all about programming teams about it.

Do you know any research about walking around the programming teams? Do you have any experience in this kind of work?

Edit: Other teams of the company, such as the Database Administrator Team, Help Desk Team, Communication Team or Network Administrator Team are already working on shifting, Do not like it but they do it anyway. I think the boss wants that we work on rotating due to them, but since we only do programming, I feel that the effect of rotating change is at least different for us.

Changing things to change things does not look like a good idea in any organization Also, The shift work was shown to inspire (a collection of factors that increases your risk for multiple negative conditions, diabetes, cancer and heart attacks). .


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -