The important thing here, is that as a CONTRACTOR, I am ONLY billing for the 60% of the "work day" that I get something tangibly, measurably, DONE. That is very important.
Chris Burbridge's List: Productive Work Time
-
Jun 27, 12
Well to the point. When the software architect started explaining our roles in the AGILE methodology, she said that our work-time in a day is expected to be only 6 productive hours, not counting lunch break; and she said it like we should already know it. So that means, if we're 9 hours at work, 1 would be our lunch break, 2 to just relax, and 6 to work. I was astonished by this remark since in my then short work experience I have had never heard anything like that.
-
-
-
So that's great! That means that when I work an "8 h our day", in terms of billed hours, 4.8 (okay—5) hours is perfectly reasonable! Because—I have to BILL for all those hours I work, and only those I work!
That could also mean, that if I want to make $85 "an hour", I should really multiply that by 1.667 to get a REALISTIC idea!
Or right now, I'm working at a rate of $60, but a lot of hours, for these guys.
It ALSO means that 25 hours a week IS REALLY what "a 40 hour workweek" is!!!
What is also cool about this, is that I actually ENJOY working 3-5 hours.
-
-
She was actually quite optimistic. In IT, a common project manager's guideline for productivity is 60% of the time available.
-
-
-
People work an average of 45 hours a week; they consider about 17 of those hours to be unproductive (U.S.: 45 hours a week; 16 hours are considered unproductive).
-
-
This is still close to that 2:3 ratio of productive to non-productive.
Multiply this from a 40 hour workweek, and you have that same 25 billable hours.
-
-
1 - 3 of 3
20 items/page
List Comments
(0)
List Info
3 items | 2 visits