General rule
There is no situation in the project department:
1. "I thought ..."
2, "This is their business, nothing to do with me ..."
3,
Task Assignment
Applicable object: development, test, demand manager
Recommended Tools: MS Project Server 2003
The principle grasp:
1. Develop a task plan based on the actual completion of the actual completion and task, and the task bearer and the distributor are required to develop together.
2. Generally needed to be overall for a month or a quarter task, but for different phases of the software lifecycle, the test group can control the periodic cycle of task within or a shorter period of time.
3. If in a period of time, in order to facilitate cooperation with other staff, the unit personnel need to complete a few tasks at the same time, and you can make the resource percentage of the task to make a coordination plan, but the sum of resources cannot exceed 100%.
4. After the task is allocated, the task distributor must communicate with the task recipient within half a business day, the purpose is: the task confirmation, the task Q & A, task is troubleshooting
Demand manager allocation task
l The demand manager must develop a task plan within the scope approved by the project manager.
l The completion time of the unit task cannot exceed 5 working days, otherwise this task needs to be refined.
l You can assign different tasks for demand engineers within a time period, but the sum of resources consumed by each task must be 100%.
Test manager allocation task
l In the software lifecycle, the task allocation of software R & D and maintenance has many different characteristics need to be treated separately.
l In the unit test phase, the test manager needs to formulate the corresponding test plan according to the task of the development group, and do tasks to people.
l Generally developing a week of task plan is more scientific, and due to the development of the cause of the task, this part of this factor requires the test manager into the risk management plan. More scientific methods are, cultivate the testing process of testing engineers, this part of the work will be described separately in later chapters.
l In system testing and maintenance phase, the test manager can make task allocation based on the plan proposed by the maintenance target, generally in accordance with the actual completion cycle plan, during which the buffer time needs to be left, the buffer time generally accounts for 20% of the total completion time. It is advisable.
Development manager allocation task
l In the unit test phase, the completion time of the unit task cannot exceed 4 working days, otherwise this task needs to be refined. Weekly task allocation needs to leave a day BUG modification time, which is conducive to ensuring the completion of the quality management plan. If the software delivery date is urgent, the elastic overtime system can be implemented. Generally, each working day needs to increase 1.5 hours as a bug modification time, while no longer retains a separate bug modification time during weekly task assignment. It is not recommended to overtow the weekend.
l In system testing and maintenance, the completion time of unit tasks cannot exceed 5 working days, and the task cycle of unit staff is suitable for long-term tasks, so that the task recipient has a holistic concept for the task you bleave, it can be fully Play its ability.
project manager
l In the unit test phase, the project manager mainly is the priority level of the task, that is, those modules should be done first, those tasks can be ranked behind. At the same time, according to the previous data and experience, the final phased workload and completion time are determined, and the task completion plan for each group is based on this, and the risk management plan is developed.
