Agile Software Development Practice-sprint Task Split

Introduced:

After running the sprint Setup meeting, and after all the story point is reasonably estimated, the next step is to story each developer/tester to build sub-task under story. The key question here is how to use the team's human resources more efficiently and make the most reasonable allocations.

Implementation mode:

This is actually based on skill set, because we all know that a team of people, experience are not level, there are senior/intermediate engineers, there are experts in this field, some are good at another area.

So our team, the first thing we did last year, was to collect everyone's skill set. So that teams leader can better understand each person's strengths and weaknesses, thus more scientific distribution of tasks.

A skill set is often an Excel table, where my skill set (partial) is basked in

After having everyone's skill set, I will make a reasonable assignment according to the team situation, if the sprint estimates the total story point many, the team will be very busy, then I will as far as possible according to skill set assigned tasks, Story to the people in the field who are best at doing it to reach the ultimate speed. If sprint estimate is not very busy, then I will let everyone to choose story, try to do what they do not good, so that you can more effectively improve the overall combat effectiveness of the team, and can learn from each other and improve together.

After allocating all the story, I'll have the team build their own sub-task under their own story, and give the estimated time to the developers themselves, because they have a better understanding of their own speed. The results of others ' calculations have no meaning for him. This time is actually not too accurate, as long as it is not too outrageous on the line. (Do not appear to modify a page of a form of JS checksum 10 hours This difference can be), and then everyone to establish a good sub-task, I and the module responsible will be in turn review each sub-task.

Summarize:

(1) Assign story to each individual proposal according to skill set and sprint progress to decide, if time is abundant, try to distribute everybody do oneself not good at module, field to achieve the function of the training and construction team, if time is compact, try to distribute according to the highest skill set to ensure the project on time delivery.

(2) The establishment of sub-task must be timely, it is best to story determined immediately after the establishment, rather than to wait for the story began to build, so as to ensure that burn down chart more good-looking, And the sub-task must be responsible for the review to make sure that their time estimates are reasonable.

This article from the "Cohesion of parallel Lines" blog, please be sure to retain this source http://supercharles888.blog.51cto.com/609344/1261180