Agile development with tools-9

Now that we have the product backlog, let's assume that we have already put a lot of functions in it. Of course, if we put it here, we will not talk about it. It's just a question of which button to click, if we say it is too detailed, we will introduce the product, rather than talking about agility.

 

Since there is already water in this pool, the next thing will begin to let the water off, a little bit at a time. Previously, scrum has incremental iterations. So what is iteration? In short, iteration is a cycle, which may be a week or two weeks. Generally, the time is not too long. In this cycle, we will take out some function points from the pool and send them out. We need to have available versions for QA to pass the test. After one cycle is completed, it will be followed by another cycle. In scrum, such an iteration cycle is called a sprint, and Chinese is called a sprint.

 

Now that we want to put the feature points in a sprint, we have to determine which features need to be put in the sprint. In this way, we have to begin a term involving scrum: Sprint planning meeting, chinese translation into plan meeting. What does this mean? It mainly involves the following:

1. Determine which features need to be completed in this Sprint

2. estimate the time required for each function point

The Project Manager, product manager, and even designer will give a brief introduction to what these functions do, and then the relevant developers will discuss how much time is required. In the end, we will come to the conclusion that a sprint cycle is fixed, so the time consumed due to the difficulty of developing functions may increase or decrease some function points, of course, the removed functions will still be completed in the next sprint.

 

Of course, the plan cannot be automatically opened by the devsuite system. It requires administrative arrangements to convene some people in the conference room. (In scrum, the main factor is actually people, design, programming, and testing are all human dependent, tools are only auxiliary, and talents are decisive), but devspec needs to be opened to explain in the process. In the devsuite system, each function point has two main attributes defined:PriorityAndDegree of urgencyIn general, it is determined through these two attributes to determine what functions the sprint needs to do. The priority is high and urgent. Of course, it will be prioritized.

 

Another result of the Opening plan is also very important, that is, the estimated time required for each function point mentioned above, and the estimated time will be written into this function point, in the form of hours, after a day's work is completed by developers, you need to write the time spent on this function point on the day, and you also need to write the estimated remaining time, in this case, by using the time used and remaining for the development of each function point in the sprint, devsuite will provide a trend report chart, such as when the development of the sprint is expected to be completed and whether it will be extended, this trend chart is actually another concept of scrum., Burndown diagram (burndown
Report ),Our product manager and Project Manager are very interested in this figure. In the past, I often had to ask them what they were doing every day. Can they finish it on time? Now I can see from the product to what extent, reducing a lot of work. Of course, you still need to use administrative commands to let employees fill in those time values carefully and get real conclusions only when real data is available.