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

What is Agile Development Scrum? The general understanding of agile development Scrum may stay at the conceptual level, and the understanding of Scrum usage methods is relatively small. Today I want to talk to you about Scrum.

1. Introduction to Scrum

Scrum is an incremental, iterative development process, named after rugby scrum. Scrum's overall development cycle consists of several small iterations, each called a sprint, and each sprint is typically 2 to 4 weeks long. In Scrum, requirements for a product or project are managed using a product order, which is a list of requirements sorted by business value, and the list entries are typically embodied in user stories. The development team always develops requirements that are of higher value to the customer first. In each sprint, the development team selects the most valuable requirements from the product order for development. The requirements selected in the sprint are analyzed, discussed, and evaluated at the planning meeting to produce a list of tasks for the sprint, which we call the sprint order. At the end of each iteration, the development team delivers potentially deliverable product increments.

The main roles of Scrum are: Product Owner, Scrum Leader, and Development Team. Scrum meetings include planning meetings, review meetings, retrospective meetings, and daily stand-up meetings. Scrum documents are: product orders, sprint orders, burn-out charts. The Scrum method is an iterative process of product development, which is carried out by the Product Owner, the Scrum Leader, and the Development Team through meetings defined by Scrum according to the necessary documents of Scrum.

Practical Application of Scrum Method

Scrum method gives a framework, how to practice Scrum according to this framework, especially how to make good use of daily standing meeting, review meeting and review meeting, are the key factors affecting the effect of agile development. There are more or less specific problems encountered in the practical application of Scrum. According to the experience of agile development projects, the author briefly analyzes these problems and gives effective solutions.

2.1 Daily Standing Meetings

Daily stand-up meetings are mandatory meetings for the Scrum Leader and Development Team members. It is an effective way for development team members to communicate in addition to face-to-face communication. Scrum advocates daily stand-up meetings that average no more than 15 minutes, and each member of the development team answers three questions to the Scrum Master: What did you get done today? What are you going to do tomorrow? Are there any obstacles to achieving the goal?

Daily stand-up meetings require effective organization by the Scrum Master. The most common problem with daily stand-up meetings is that team members get caught up in discussions about specific technical issues, resulting in significantly longer meetings and affecting the efficiency of the meeting. Another situation is that when one member reports obstacles encountered, other members do not listen carefully, and some common obstacles or dependent problems are not paid enough attention, resulting in everyone stuck in the same problem, affecting the progress of development.

To make the daily stand-up meetings more efficient, each member of the development team needs to control their speaking time, usually around 3 minutes. the speech should highlight the main points, be concise and to the point, and should not discuss specific technical issues in detail. The Scrum Leader should alert team members when they start discussing specific technical issues, which can effectively control meeting time. In order to keep everyone aware of the current status of the project, especially the obstacles that may affect the achievement of the goals, the Scrum Master summarizes the obstacles recorded to the development team at the end of each meeting, so that everyone knows and ensures that the next day's development work is not widely affected. Doing so also helps the Scrum Master to effectively remove these obstacles for the team in the next step.

2.2 review meeting

At the end of each sprint there is a review meeting, which the Product Owner, Scrum Leader, and Development Team must attend. The purpose of the review meeting is for the development team to present to the Product Owner the functionality accomplished in the sprint, answer questions from attendees about the presentation, and document desired modifications. The review meeting process generally does not exceed 4 hours, and the development team generally does not exceed 1 hour to prepare the review presentation. The review meeting contains the meaning of phased acceptance. How to get positive recognition and effective feedback from the product responsible person within the limited display time is a problem that must be paid attention to in the preparation stage and the process of the meeting.

In the preparation phase of the meeting, the development team should organize the demonstration points of product features according to the sprint order of this sprint, and form a clear and concise PPT document. It is best to have an online demonstration of the actual functionality at the meeting site, so the development team should have workstations and equipment ready before the meeting. At the same time, the development team also needs to save the data such as graphs, tables and logs that can show the product function effect in advance, in case there is no content to display when the emergency situation causes the failure of the field display. At the beginning of the meeting, the Scrum Leader and the development team need to make sure that everyone understands the product and the goals of the sprint, and if anyone is unclear, take a few minutes to describe them. Then, according to the prepared PPT document, the development team introduced the results of this sprint one by one, and demonstrated its functional effects. During the presentation, the team should focus on "what we did" rather than "how we did it." This allows the product owner to have an intuitive understanding of the current functional status of the product, rather than getting bogged down in technical details. If the Product Owner wants to change something, the Scrum Master adds the requirement to the product order and leaves it for later sprints.

2.3 Review meetings

A retrospective meeting is held at the end of each sprint, usually after the review meeting, to summarize the practical experience of the sprint and point out areas for future improvement for the team to avoid repeating the same mistakes. The Scrum Leader and Development Team must attend retrospective meetings. Review meetings are important meetings in Scrum methodology, and they can be used to improve team productivity. The retrospective meeting needs to encourage team members to actively participate and brainstorm, otherwise, the meeting will become a formality and will not achieve the desired effect.

In practice, retrospective meetings can take the form of brainstorming. At the beginning of the meeting, the Scrum Leader summarizes to the team members the results of the implementation of the improvements identified at the last Sprint review meeting. Then, the Scrum Leader gives each member a Post-it note to think about, review what the team did well and what it did poorly in the Sprint and what needs to be improved, write three comments on each note, and then paste the note on the whiteboard. Once all members have posted their notes on the whiteboard, the Scrum Master and team members discuss the comments on the notes one by one to fully understand what the team members are thinking. During the discussion, the Scrum Master merges similar opinions and sorts out issues with dependencies. At the end of the retrospective meeting, the Scrum Leader will be informed of what went well and what needs to be improved in the sprint. Those that need improvement are tracked at the next sprint review meeting.

3. summary

The Scrum methodology is a framework for agile development that does not specify specific practices. Scrum advocates flexibility and follows the people-oriented principle of agile development, which requires software project managers to choose appropriate solutions based on factors such as enterprise culture, management model, and experience of development teams.

After reading the above, do you know more about Scrum? If you want to learn more skills or want to know more about related content, welcome to pay attention to 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.