-Step 1: income the characteristics of the product (backlog) in order. This is the most important step. Set up the working team, able to split into teams if needed and talk with each other about the profession needs to do. Then appoint a person to the location of the Product owner, who has the ability to Exchange, covering a good work, know the sort order priority tasks. Then reorganized the team work, suggestions out location of Scrum master and discussed in detail the requirements, arrange them in order of priority.• Step 2: estimate the full requirements for product output. There is a high level estimate, divided into product categories number of backlog. However the amount will not exactly be, later on they will be added. Next up is the estimate in detail each of the backlog, the estimate for the number of working teams.• Step 3: planning the development of sprint loop. Use the Exchange development sprint plan with all the members. Determine the period of time will develop a sprint (usually 30 days), sprint's goal is nothing, will achieve anything, analyzing the requirements of sprint in a clear way.• Step 4: plan the development tasks of the sprint. All the people will determine the budget of sprint, divide the characteristics into smaller tasks, estimate of time will do each task (hours), complete the request and identify the important task.• Step 5: create collaborative workspace for all people. Often use the White Board to draw up the necessary matters for all people of the same rank.• Step 6: members began construction of each sprint. Programming, testing and tuning time to have the best effect. Can sometimes remove a sprint and returned with other planning.• Step 7: people results reported to continue working. The reports focus on the issues: what was achieved compared to the previous Exchange times; will complete what in the next Exchange; what obstacles are in the process of work etc.• Step 8: General results on the chart. This is the general picture of the work done, the job is not yet done, estimated time left and adjustable back.• Step 9: review to complete. When members said the work has been completed which means that any changes will be rejected, pushed back to the following loop.• Step 10: evaluate, reflect and repeat. Have the meeting reviews the sprint again by members. Will present what gain, customer feedback, considering the duration of the sprint. Look at the diagram in step 8 to redefine the entire system and receiving contributions, additions to put next to the loop for the next sprint.4. StrengthsThe strongest point is that the flexibility, the project will not be fixed from the beginning of time complete or the requirements that it should be determined when the actual development.Flexible product delivery: delivery of product content is determined according to the flexibility the environment use the fact. Flexible schedule: may later or earlier than originally planned.Good product quality and reduce production risks, low cost. The ability to exchange between the client and developer, between the team members are putting up high.Fast development speed, saving time. The preparation of the action for the changes in the process of developing better because almost daily there are always the meeting reviews back in the development loop.The bugs (bugs) and problems to be discovered sooner than traditional methods because customers are involved greatly appreciated and the output of the product very quickly. And when going the wrong direction, can cancel right sprint to come back with a plan.
đang được dịch, vui lòng đợi..