Sometimes you may have to make a work arrangement, over time, will also explore a lot of experience in improving efficiency and reasonable organization. The theory of talks can not be practical, to ensure the reasonable, controllable and efficiency of the plan is not an easy task. Now I have to say an English: schedule. Like a special language in all industries, for software engineering, the connotation of Schedule has transcended the meaning of the "schedule".
The author advocates the schedule plan, but the specific practical means each has a thousand autumn, and Schedule can be said to be the agreement of all participants.
The Schedule meeting is a better way. Everyone can say their own point of view, and you can understand the views of others, and finally form a unified comment, then it is executed. SCHEDULE meeting has proposals -> Discussion -> Voting, and Program -> Explanation -> Resolution, the purpose is to let participants understand what to do and the goals to achieve, the most important thing is to understand the specific steps. A small problem solves so many key issues, it is really not much.
Schedule reflects a small process perspective, referring to its mode arrangement, in line with the general law of solving problems. Summary is as follows:
1 Under the premise of work goals, the timetable of the various tasks is developed.
2 execution schedule
3 Summary Analysis of Planning and Performance
In the introduction, the author wrote: Completing the purpose of this series is to "explain the methodology of a software practice", in fact, the change is not from its Zong, and is called "closed loop coordination".
Let's take an example (slightly some real name, in order to use the universal name).
() 1. User's manual checks the release (the name of the name)
2, the test project is completed
() 2.1 Questions 1 Confirm (as a name)
() 2.2 Test Project 1 Confirmation (Responding to Name)
3, the installer report and program backup remain up to date
() 3.1 Program module 1 Source backup and fill in the installer report (the name of the name)
() 3.2 Program module 2 Backup and fill in the installer report (the name of the name)
() 3.3 Program module 3 Backup and fill in the installer report (the name of the name)
() 3.4 Print Module Fill in the installer report (the name of the name)
() After the first step is completed, the installer is produced (the name of the name)
() 3.6 System Administrator's Manual (Looking at Name)
() 3.7 Backup file structure table. Xls (the name of the name)
() 4. Software demand instructions final (the name of the name)
() 5, the program sent to the user update (the name of the name)
() 6, generate the test document separately save (as a name)
() 7. Database backup (with name)
() 8, test database backup (the name of the name)
() 9, all data compression backup 2 CD (as a name)
() 10, only 2 CDs of the software installer (the name of the name)
() 11, test work Project document. MPP (the name of the name)
() 12, project summary (with name)
This is a timetable for work on the software issuing phase, 6 people work within 1 day, if an item has been completed, hook it in parentheses. Again, the accumulation is formulated, and it is called a standard. At this end, I will run again.
