Shulou(Shulou.com)06/03 Report--

Today, the editor will bring you an article about the Scrum agile development sprint. The editor thinks it is very practical, so I will share it for you as a reference. Let's follow the editor and have a look.

In the process of agile development, a product or a release is usually implemented by multiple sprints, each of which can incrementally deliver runnable system functions to achieve customer value. Each sprint starts from the sprint planning, the team members agree on the sprint goal and clear delivery of the system function, and carry out the sprint execution to realize the system function, and then review the realized product function and process through sprint review and review. It is expected to improve and improve the product function and process in the next sprint process.

Sprint process

The sprint includes four processes: sprint planning, sprint execution, sprint review and sprint review. The sprint starts from the planning, and the team members must reach a consensus on the goal and plan of the sprint, and all members move forward to this goal in accordance with the established plan throughout the sprint process, and communicate and discuss the achievements and problems they face every day. At the end of the sprint, the relevant stakeholders are convened to demonstrate the product function and get feedback in the sprint review activity, which is an important source of the product list and the content of the next sprint planning. In the sprint review activity, all team members review and discuss the sprint execution process, grasp the existing problems and discuss the optimization scheme, and improve and optimize the next sprint to achieve the optimization of the sprint process and the improvement of sprint execution efficiency.

Sprint planning

In general, sprint planning is carried out at the beginning of each sprint, because at this point in time, you can make the best decision by making full use of the information you have. The length of the sprint planning process depends on the length of the sprint, and it is reasonable to occupy about 5% of the whole sprint. For example, a two-week sprint should be controlled within 4 hours, and an one-month sprint should be controlled within 8 hours.

The sprint planning process should be completed by the whole team, and the product owner selects the individual items from the existing product list, puts forward the preliminary goals of the sprint, and is responsible for explaining any questions raised by the development team about the selected product inventory items. The development team evaluates the to-do list that can be delivered within the sprint and makes a final commitment at the end of the planning. As a coach, Scrum Master participates in and observes the whole process, proposes possible risk points, guides and helps the development team to make effective commitments.

In the sprint planning process, the basic process is:

At the end of the sprint planning process, the sprint goal and sprint list are finally obtained, and the development team makes a commitment to this goal and to-do list, and strives for this goal in the following sprint execution.

Sprint execution

Sprint execution, which includes all the work that must be done to deliver an incremental releasable product, is like a ultra-small project, and the sprint execution process takes up most of the sprint time, such as a two-week sprint. Sprint execution takes 8 of 10 days, so the sprint execution process is essential to the successful completion of the sprint goal. Sprint execution includes planning, management, execution, and communication:

01 Planning

Sprint execution planning can sort out dependencies on important work items in the sprint list, but you don't need to make a detailed execution plan, such as a Gantt chart, because it can be a waste of time. The team not only wasted time making the plan, but also wasted more time trying to adjust the plan to reflect the real implementation. The principle of sprint implementation planning is to act on the occasion and gradually clarify the task planning. this activity is continuous and runs through the whole sprint implementation process.

02 management

Sprint executive management is a management activity to ensure that the sprint goal is achieved. The characteristics of the development team determine the management style. Sprint executive management specifically needs to solve the following problems:

How many work items should be in parallel? If there are too many parallel work items, team members will switch between different work items, resulting in waste; too few parallel work items will also cause idle waste of resources, an appropriate number of parallel, and strive to make full use of the team's production capacity, but not too onerous, to achieve a reasonable balance, which requires each team to practice and explore according to its own abilities and characteristics.

Which work item do you start with? The simplest way should be to order the priority from high to low, but in the specific implementation process, you may encounter a variety of problems so that the high-priority work items can not be started temporarily, in this case, you can also start the second-highest priority work.

Who will do it? The most obvious answer is for the person who can do it best and fastest to do it. But each team has its own considerations, such as the most suitable person may be busy with other work, or he may be on vacation, or even from the perspective of team development, other members can be given the opportunity to exercise, in order to achieve the overlap of team members in various skills, complement each other.

The daily meeting is a key daily review-adjustment activity, which is limited to 15 minutes. The main purpose is to review, adjust and synchronize daily work plans to help the team do a better job.

03 execution

For Scrum agile software development, team members need to be proficient in some application software development technical practices, such as continuous integration, automated testing, refactoring, test-driven development, etc., these technical practices will put higher requirements on the development team, and will cause progress or other pressure on the development team in the short term, but in the long run, only actively use these good technical practices To actually experience the benefits of Agile.

04 communication

Agile teams are generally small enough that small team members do not need complex charts and reports to communicate work progress. The following methods and tools are recommended:

Task board: displays the task status of the sprint list over time.

Sprint burnout chart: shows the remaining workload curve of unfinished tasks.

Sprint combustion chart: shows the workload curve completed in the process of achieving the sprint goal.

Sprint judge

Sprint review focus on the product, that is, focus on the results, review the results of the work completed during the implementation of the sprint, including the Scrum team, internal stakeholders and external stakeholders. An important preparatory work before the start of the review is to confirm that the sprint work is completed, which is done by the product owner, who finally confirms whether the work items in the sprint list are completed, and the time for confirmation is not until the last minute before the review. it can be confirmed as early as possible in the sprint implementation process, which will find the problem as early as possible and win the time to remedy.

The methods used in the sprint review process include:

01 Summary

Usually the product owner gives a general description of the work of this sprint, and shows the sprint goal and sprint list, explaining the basic situation of the completed product increment.

02 demo

The completed system functions are demonstrated by the members of the development team, and at least some test programs are provided to prove that the completed work meets the requirements of the product owner for those functions that are not easy to demonstrate (such as programs running in the background). The presentation that needs to be noted is not an end in itself. The purpose of the demonstration is to stimulate the thinking collision of team members and to put forward more constructive suggestions and feedback.

03 discussion

The incremental demonstration of the product guides participants to comment, establish and discuss appropriate aspects of the product features or objectives. If more in-depth discussion of the problem plan is needed, a separate meeting should be held independently.

04 adjustment

Through demonstration and discussion, there will be some changes or new requirements, which will adjust the product list and the sprint list in the next stage. after combing, you will get an updated product list at the end of each sprint, and you can respond to changes in time in the following sprint.

Sprint review

The sprint review focuses on the product construction process itself, that is, the process. The team will review what happened during the sprint, analyze the way they work, identify possible problems, propose improvement plans and make improvement plans. Before each sprint review, you can define the focus of the review so as not to be too scattered. In the review meeting, you need to ensure that the atmosphere of "not the right person" is created, and that the purpose of the review is to improve the process, not to blame a person. At the end of the review, ask team members to follow up and implement improvement measures to make the team more efficient in the next phase of the sprint.

Summary

Sprint includes most of the time and activities in the development and management of the whole product or project, and is the main link in the realization of product function. This paper attempts to discuss all the activities and work involved in sprint from the point of view of sprint planning, sprint execution, sprint review and sprint review. I hope it can give some inspiration and help to the agile team in the implementation of the sprint process.

After reading the above, do you have a general understanding of Scrum agile development sprint? If you want to know more about the content of the article, welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.