Read Homework 1-read questions and feelings about the path to mountains

I recently read instructor Yan Xin's "The path to mountain migration" and found an interesting thing when I was reading the third article of teamwork: "Most people have reflected that the previous project was too busy, when everyone worked overtime, but did not get the result, the Alibaba Cloud team discussed the schedule. "

It is pointed out that employees only work 40 hours a week, eight hours a day. Working hours are the company time, and project work hours are the time when you develop projects with concentrated energy and no interference. Based on experience, each person has a maximum of four days a week, and 32 hours are actually working on the project. The remaining 8 hours are described in the following three aspects --

(1) In daily affairs, we do have to spend a lot of time dealing with trivial things that have to be done: communication, meetings, discussions, email writing, and playing games (!) For some employees, 8 hours is not enough.

(2) as a buffer, if your task is not completed, use this time first. This shift means that if the task of your project is not completed, you will have less sessions, discussions, and games.

(3) There are many emergencies in the project process. If you want to respond to emergencies, you can set aside time here. If not, you can get it from the 32-hour working time.

Because of the different division of labor, different employees may have different "non-development time". For example, managers may need extra time for management. I found that, for those managers, testers, and project managers, the final quality of the module determines the work performance. For other frontline personnel, it may beCodeThe number of rows and quality determine the job performance. I have some questions about the lack of relevant work experience. Such a schedule seems to be determined by default based on the above final evaluation criteria based on the 32-hour (or other) workload per week, does that mean 40 hours of work time, 32 hours of work (assuming) quality assessment, people who have completed the fast speed may think they have extended the "non-development time" for daily transaction processing? An 8-hour non-development period in a week can be either private or official. can or should this 8-hour period be included in the performance evaluation? How should a Team coordinate everyone's "development time" and "non-development time"? Do they fully authorize trust or anything else? How can we determine the 8-hour plan? Can other teams continue?

Of course, I still feel better about this kind of human arrangement. The assignment of tasks is issued, and the following persons are responsible for completing the work (How do I feel like at school: The teacher assigns homework and the students finish the work on time, the instructor scores the score based on the assignment completion: ABCD ). In addition, I would like to ask if there are other better time schedule methods?