Chapter 2 Time Management
U time management logical principle
u Understand time usage
2.1 Time Management Logical Principle
People are likely to arrange this week in the last week. Of course, as work, there are many exceptions.
In order to develop a practical plan, it is necessary to track the time used. If you ask how it is useful last week, the average person thinks it is easy to spend every work, but when you see the actual data, it is very surprised when you see the actual data: spending more time than estimated Less less, spend more time than expected; happy things do especially, it seems particularly small, and the time to take a distress thing seems to be much more than the actual cost. . To figure out where time is used, you must track the time, keep an accurate record.
In order to check the accuracy of time estimation and plan, they must be written as a document and compare them in the future. Doing a plan is a skill, learning to formulate a good plan, the first step is to do plan first, then write the plan to compare it in the future.
In order to develop more accurate plans, it is necessary to know which errors in the previous plan, which places can be improved. When working in accordance with the plan, the time spent will be recorded. By comparing documentation plans and actual results, you can find what errors exist in the plan and how to improve the process of making a plan. The key to formulating an accurate plan is to adhere to the development plan and compare each plan with the actual results, and then know how to make a better plan.
In order to manage good time, first develop time allocation plans, then follow the plan. The production plan is easy, but the truly implementation plan is difficult. At the beginning, it may be more difficult to work in accordance with the plan. You may have a lot of excuses, the most common thing is that this plan is not good. But only according to the plan, you can know its pros and cons.
There are three advantages to work in accordance with the plan: First, what problems have to be found, which helps better plan the next project. Second, complete the work in accordance with a good plan. This doesn't seem to be important, but in fact, many mistakes in the software engineering are due to consideration of not-week, careful or unaware of small details, and the best way to avoid these mistakes in accordance with good planning work. Another more subtle advantage is that it is actually changing your way of working. If you have a plan, you don't have to waste time. If you want to do it, it will help you concentrate on the things, very small, Thereby improved work efficiency.
2.2 Understand the use of time
Classify primary activities. When you start allocation time, you will find that most of the time is used in relatively few activities.
Record the time spent on each primary activity. Adhere to the recording time requires a strong self-constraint ability, to make accurate records, must record the time for each main job and end. Unless you know how much time you actually use, it is impossible to manage the way of use.
Record the time with standard method. Standard time logs must be used. Because the number of time data that needs to be collected is fast, if you do not carefully record and store these data, they are likely to lose or become chaotic, which is very disadvantageous to find or explain them. If you don't intend to properly organize these data, you will not be necessary to collect data at all.
Table 2.1 Event Log format
date
Starting time
End Time
Interrupt time
Net time
activity
Note
C
U
Note: c means "completed", u means "unit"
In minutes as the measurement unit. The engineering is that the time of uninterrupted work in the completion task is generally less than 1 hour, so the working time is measured in hours in hours that cannot provide detailed data needed to plan and manage the work, and the time to track the time is much easier. . Once the time tracking is decided, it will use minutes as the measurement unit more appropriate than the hour. Processing interruption time. When using Table 2.1 Tracking time, a common problem is interrupted. The number of times the phone, chat, occasional troubles and the necessary rest interruptions are surprising. The interruption time is not a valid working time, and the change is large. If it is not measured, it is actually added to the time record, it is difficult to use time data to plan and manage time. Data in the event log can help you understand the frequency of work being interrupted. Most interruptions not only have time, but also interrupt your ideas, leading to efficiency reduction and errors, so it is understood that the frequency of interruption helps improve work quality and efficiency.
Save time data in a suitable place. Recording time spending the recommended method is to use engineering notes to record time and other things. For a software professionals, engineering notepads can be used, and the time logs, programming schemes, and calculation results can be recorded. As you can follow the correct project implementation, you can record a flashing idea in your mind. The recommended method is to record the main activities and the time it takes from the first page of the engineering notepad, and the last page starts to record the time log forward. The primary activities and the time they spend, the last page starts to record the time log forward.
Summary of the week. After using the time log collection time data, you can gradually understand how you give a time. However, the data in the time log is too detailed. You need to use a more useful form to summarize these data, and the weekly activity summary table can complete this task. Of course, our time is not only such a short one week, but also take average time, maximum time and minimum time spent on various tasks. Therefore, the format shown in Table 2.2 is used. The data in the weekly event summary table can help you understand the time in those places, and you can also use these books to plan a few weeks. For example, with this data can determine that a large task needs to be close to the maximum time in the summary table, while a simple task requires time to approach the shortest time.
Recording time prompt. Always prepare the engineering notepad; when you think about the recording start time, end the event or interrupt time, make an estimate as soon as possible; timely summarize the time data of the record.
