Timeline for Are 40 hour work-weeks (no overtime) acceptable for development teams?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2013 at 11:25 | comment | added | Kelly Tessena Keck | Martin, in my (US) experience, most employees aren't on contracts at all, but are "at will" employees. Yes, of course, if you have a contract that sets the work hours and location, that limits your options. | |
| Apr 13, 2013 at 16:55 | comment | added | Martin Schröder | If you want to go that way, start with the contracts. If the contracts state that employees have to work 40 hours a week, this is a non-starter - as the contracts really state that the employees have to be at the office for 40 hours a week. Good luck with getting ROWE in the contracts - you'll probably end up with having contractors instead of employees. | |
| Sep 2, 2012 at 13:19 | history | edited | Kelly Tessena Keck | CC BY-SA 3.0 |
grammar correction
|
| Sep 2, 2012 at 13:17 | comment | added | Kelly Tessena Keck | Good point, CodeGnome. I'll edit to add that. | |
| Sep 1, 2012 at 22:26 | comment | added | Todd A. Jacobs♦ | +1 for focusing on the results, but I'd also add that expectations still need to be reasonable, and folks should only be on the hook for work that they've made a personal commitment to perform. | |
| Aug 31, 2012 at 20:05 | history | answered | Kelly Tessena Keck | CC BY-SA 3.0 |