A survey of Agile development methods

A survey of Agile development methods

The traditional software engineering method is more and more difficult to adapt to the rapid updating of the software requirements, so the formation of a number of light-weight development methods, this is known as the rapid development of software requirements for the agile approach. The agile development takes the user's demand evolution as the core, uses the iterative, the gradual step method carries on the software development. In agile development, software projects are cut into multiple sub-projects in the early stages of construction, and the results of each sub-project are tested for visual, integrated, and operational use features. There are many approaches to agile development, including scrum, extreme programming, functional-driven development, and unified processes. This is the main discussion of the scrum approach.

The scrum Master, a coach, a shepherd dog, is the maintainer of the Scrum project order. He is responsible for managing the scrum process to ensure that scrum is working properly.

The product owner is responsible for managing the product backlog and maximizing the value of the project.

The team is the cross-functional team responsible for developing the software. The team is self-managing and with the help of Scrum master, the team promises to fulfill its commitments and realize the value of the software. The main steps of the scrum methodology are as follows:

First, find out what needs to be done (product backlog), build a backlog entry, refine the entry information, and prioritize the goal. Describe the story title, priority, story in detail. The product owner is leading everyone to this backlog

Work on the increase/deletion/change. Each work time is estimated to be "days".

Second, decide what the current sprint needs to solve. At this stage, teams and product leaders are required to work together to develop a sprint goal. Focus on this goal throughout the sprint. The implementation of the entire product is divided into cross-linked sprints. The tasks on the product order are further refined and broken down into hours. The task on the order is that the team members claim according to their own situation, the team members can help to estimate and assign the task, their initiative is greatly played.

Finally, in the sprint phase. External personnel cannot directly disturb team members. All communication intelligence is done through Scrum master. This measure is a good balance between the "exchange" and "concentration of attention" contradictions. During the sprint, every day to open a daily meeting, the team members are mostly standing in the meeting, so there is called Hitachi. Daily meetings Force everyone to report progress to their peers, forcing everyone to put the problem on the materializing, so that everyone can see a gradually improved version every day.

The above is a summary of the scrum methodology for agile development.

A survey of Agile development methods