|
|
|
- [[Japanese]]
|
|
|
|
* Part II Office Environment and Productivity
|
|
|
|
* [[Chapter 7 Equipment Police]]
|
|
|
|
* [[Chapter 8 The program can be done at night]]
|
|
|
|
* [[Chapter 9 Saving Office Investments]]
|
|
|
|
* [[Break a minute... Intermezzo]]
|
|
|
|
* [[Chapter 10: Mental Labor Hours vs. Physical Labor Hours]]
|
|
|
|
* [[Chapter 11 Phones, Phones, and Phones]]
|
|
|
|
* [[Chapter 12 Restoration of the Door]]
|
|
|
|
* [[Chapter 13 Office Environment Evolution Theory]]
|
|
|
|
|
|
|
|
## Chapter 10 Brain work hours versus physical work hours
|
|
|
|
|
|
|
|
Table 10.1 Ratio of working hours by work status
|
|
|
|
|
|
|
|
|Working status|Ratio|
|
|
|
|
|:-:|:-:|
|
|
|
|
|One person work|30%|
|
|
|
|
|Work by 2 people|50%|
|
|
|
|
|Work by 3 or more people|20%|
|
|
|
|
|
|
|
|
- Flow state and productivity
|
|
|
|
- Percentage of average hours worked per day as surveyed by IBM (Table 10.1)
|
|
|
|
- Working alone is a minority, but **real work can be done when you are alone**, so you can't ignore it
|
|
|
|
- In a noisy office, it is impossible for a programmer working alone to be in a **flow state**
|
|
|
|
- Anything that distracts you reduces programmer productivity and significantly increases the cost of your project.
|
|
|
|
- e.g. the states in Table 10.2
|
|
|
|
|
|
|
|
Table 10.2 Example of work content and work time in programming contest
|
|
|
|
|
|
|
|
|Work time (start to end)|Work content|Cause of work interruption|
|
|
|
|
|:-:|:-:|:--|
|
|
|
|
|2:13-2:17|Coding|Telephone|
|
|
|
|
|2:20-2:23|Coding|My Boss's Stupid Talk|
|
|
|
|
|2:26-2:29|Coding|Questions from Colleagues|
|
|
|
|
|2:31-2:39|Coding|Telephone|
|
|
|
|
|2:41-2:44|Coding|Telephone|
|
|
|
|
|
|
|
|
- Write physical work hours instead of mental work hours on time cards
|
|
|
|
|
|
|
|
>It doesn't matter how many hours you've sat at your desk, it matters how long you've worked with all your attention.
|
|
|
|
|
|
|
|
- How to calculate the time actually spent on software development
|
|
|
|
- **Record the number of consecutive uninterrupted hours** (mind concentration time) for each person
|
|
|
|
- Still record manual hours for payroll
|
|
|
|
|
|
|
|
- Two Benefits
|
|
|
|
- Draws attention to the importance of flow time: people start to take at least a few hours of uninterrupted time for granted
|
|
|
|
- A true record of time spent on work: It is NG to analyze the accumulated flow time against the flow time required to complete the project on a physical labor time basis.
|
|
|
|
|
|
|
|
$$
|
|
|
|
E-Factor = \frac{ \text{ Number of hours without interruption } } { \text{ Hours spent sitting at desk } }
|
|
|
|
$$
|
|
|
|
- E factor (environmental factor)
|
|
|
|
- Daily measurement of the E-factor formally acknowledges the idea that programmers need some uninterrupted time.
|
|
|
|
- By pushing the E factor to the forefront, we can change the corporate culture in the direction of not interrupting work.
|
|
|
|
|
|
|
|
→ A corporate culture of uninterrupted time logging helps programmers have time to do real work |
|
|
\ No newline at end of file |
