Summarize the scrum of agile development

The concept of agile development

Agile development is a human-centered, iterative, progressive approach to development.

Why is it that people are at the core? The traditional waterfall model is document-driven, but in agile, only a small number of documents, focusing on the person-to-person communication.

What is an iteration? Iteration is a very long development cycle, divided into a small cycle, at the end of each cycle will have a deliverable product, which we call an iteration.

Scrum is a kind of agile. (Scrum is used by our company)

Scrum the three major roles:

PO (product owner): The products owner, mainly responsible for the team to ask for requirements, determine the function of the product, as well as the acceptance of the product.

Scrum Master: Responsible for the coordination within the entire team, protect the team from outside interference and ensure the team is working properly.

Scrum team: A cross-functional team that is responsible for the requirements of each iteration.

Scrum Process:

1.PO lists a list of product requirements by priority.

The 2.Scrum Master and po and XXX pre-schedule will determine which requirements are to be carried out in the next iteration, and what needs to be moved into future iterations.

3. Scrum team opens the plan meeting. (1) At the meeting PO to explain each Stroy (Scrum function is divided into a number of small functions, a small function is called a story) to complete the function, you have questions about these stories, you can ask questions on the spot, until there is no problem. (2) Next, we will give each story to estimate the points, the development of the development of the point, testing the point of assessment test. (3) Each member receives his or her own task.

4. The iteration begins. Every morning, the meeting was held in 15 minutes, and everyone stood together, reporting what was done yesterday and what they planned to do today. At the same time encountered can not solve the problem can also be raised at the standing meeting. After the report, go to the blackboard and move your story to the corresponding state of the Burndown chart.

5. Iterative presentation sessions: At the end of each iteration, the members need to present the story that was completed within the iteration to the other members.

6. Finally, the review will be conducted in a rotational manner, each of which summarizes the pros and cons of this iteration in turn. The host of the meeting (we are usually PO) is responsible for documenting these advantages and disadvantages. If there is a need for improvement, implement it in the next iteration to resolve the improvement.

The difference between agile testing and traditional testing:

1. Different processes:

The traditional testing stage is obvious, demand analysis, design Review, unit test to integration test, System test, test plan, test design, test execution, test report and so on.

In the agile testing, more emphasis on the continuous testing of products, quality of continuous feedback, the process is more simplified, more ambiguous stage.

2. Traditional testing will focus on the development of Test plans, but in the agile emphasis on the speed and adaptability of the test, focusing on the continuous adjustment of the plan to adapt to rapid changes in demand.

3. In traditional testing, the development and testing roles are clearly divided.

But the quality of the product in agile is not just about testing, it's more like the whole project team. For example, we testers to write the test cases, use cases are three parties (development, testing, product) to review the confirmation, so that the testers designed to find out the use of the missing and insufficient, in order to identify the product more defects.

4. Traditional testing encourages automated testing, but the success or failure of automated testing has no fatal impact on testing.

However, in agile testing, because the release version is too fast, the cycle is too short, there must be automated to assist testers to perform regression testing, otherwise agile can not be done. This means that agile testing is based on automated testing.

5. Traditional testing emphasizes that the defects found are documented to facilitate subsequent tracking of defects, analysis of defects (analysis of the root causes of defects, analysis of which priority levels in these defects need to be fixed before this release is released, which can be left to the next release), generating defect reports, and a focus on defect handling and tracking processes.

But in the agile, the more emphasis is face communication and communication, and pay more attention to the product itself, but not the defect itself.

Summarize the scrum of agile development