Agile Software Development

What is Agile development?

Agile Development (development) is a human-centric, iterative, and progressive approach to development. How do you understand it? First, we have to understand that it is not a technology, it is a development method, that is, a software development process, it will guide us to use the prescribed link to complete the development of the project, and this development method of the main driving core is people; it uses iterative development.

What is an iteration? Iteration refers to the development of a complex and long development cycle, broken down into many small cycles can be completed tasks, such a cycle is an iterative process, at the same time each iteration can produce or develop a deliverable software PRODUCT.

What is scrum? The English meaning of scrum is a professional term for rugby, which represents the action of "fighting the ball", and the name of a development process is called scrum, and I think you can imagine that your development team is developing a project, everyone is as fast as playing football, passionate about fighting, everyone you fight for me to complete it, You must be very excited. And scrum is a development process that allows you to see your team work efficiently.

The three major role product owners in the scrum development process are primarily responsible for determining the functionality of the product and meeting the required standards, specifying the release date and delivery content of the software, as well as the right to accept or reject the work of the development team.

The Process Manager (Scrum Master) is primarily responsible for the smooth implementation and execution of the entire Scrum process within the project, as well as the removal of communication barriers between the customer and the development effort, enabling customers to drive development directly.

The development team (Scrum team) is primarily responsible for the development of the SOFTWARE PRODUCT under the scrum specification process, the number of people is controlled by the 5~10, each member may be responsible for different technical aspects, but requires that each member must have a strong self-management ability, but also have a certain ability to express Members can work in any way they can, as long as they reach the sprint goal.

Scrum flowchart

What is Sprint? Sprint is the meaning of a short distance race, which refers to an iteration, and the period of an iteration is half a month (that is, 2 weeks), that is, we want to complete the development of an iteration at the fastest speed, which we call a sprint.

How is scrum developed?

1. First, we need to identify a product Backlog (a list of products in order of priority), which is the responsibility of product Owner;

2. The Scrum team estimates and arranges the workload according to the Product backlog list;

3. With the Product Backlog list, we need to select a story from the Sprint Planning meeting (Sprint Planning Conference) as the goal of this iteration, with a time period of four to 1-2 weeks, The story is then refined to form a sprint Backlog;

4. The sprint backlog is done by the scrum team, and each member is subdivided into smaller tasks based on the sprint backlog (the workload of each task can be completed within 1 days);

5. During the sprint backlog selected at the Scrum team completion planning meeting, a Daily Scrum meeting (daily stand-up session) is required, and each meeting is controlled for about 15 minutes and everyone must speak, and to report to all the members in person what you did yesterday, and to all the members of what you are going to accomplish today, at the same time to meet the problem can also be solved, the answer is completed, everyone to go to the blackboard to update their Sprint burn down;

6, to do daily integration, that is, every day to have a successful compilation, and can demonstrate the version

7, when a story is completed, that is, the sprint backlog is completed, it is a sprint to complete, at this time, we are going to Srpint Review meeting (Demo conference), also known as the review meeting, each of the scrum Team members have to demonstrate to them the software products they have completed (this meeting is very important and must not be canceled);

8. Finally, the Sprint retrospective meeting (retrospective meeting), also known as a wrap-up session, takes turns to speak, where everyone has to speak, summarize and discuss improvements, and put them into the next sprint's product requirements.

Transferred from: http://www.15yan.com/topic/scrum/domKU5booha/

P.S not understand, and then slowly understand.

Agile Software Development