Agile Development Scrum Literacy Chapter _ Agile Development

In order not to fall behind, I also began to learn scrum, today mainly on my recent reading of the relevant information, according to their own understanding, in their own words to describe the various aspects of scrum, the main purpose is two, one is to carry out the summary of knowledge, Another is that a lot of learning information on the Internet so that beginners are not easy to understand; So I decided to write a literacy blog, while also trying to share with the garden friends, hope to help beginners.

What is agile development.

Agile Development (Development) is a human-centered, iterative, step-by-step approach to development.

How to 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 specified link to step by step to complete the project development, and the main driving core of this development is human; it uses iterative development;

Why is it that people are at the core?

Most of us have studied the waterfall development model, which is document-driven, why. Because during the whole development of the waterfall, a lot of documents are written, when the requirements document is written, the developer is developed according to the document, all based on the document; Agile development It only writes the necessary documents, or writes as few documents as possible, agile development focuses on person-to-person, face-to-face communication, So it emphasizes the human as the core.

What is an iteration.

Iteration is the process of splitting a complex and long development cycle into tasks that can be accomplished in a number of small cycles, and each iteration can produce or develop a software product that can be delivered in a single iteration.

About scrum and XP

Agile is a guideline or development approach, but it doesn't tell us exactly what process is being developed, and scrum and XP are the specific ways to develop agile, and you can use the scrum approach or XP; the difference between scrum and XP is that Scrum focuses on the process, while XP is biased towards practice, but in practice, the two are applied together, and I'm mainly talking about scrum.

What is scrum.

The English meaning of scrum is a professional term for rugby, the action of "contending for the ball"; I think you can imagine that your development team is playing football as quickly, with a passion for fighting, and everyone you want me to do it, as a development process name is scrum. You must be very excited.

Scrum is a development process that allows you to see your team work efficiently.

"Three major roles in the scrum development process"

Product Owner (products owner)

The main responsibility is to determine the function of the product and meet the requirements of the standard, specify the release date of the software and delivery of content, and have the power to accept or reject the development team work results.

Process Manager (Scrum Master)

Mainly responsible for the smooth implementation of the entire scrum process in the project, as well as the elimination of communication barriers between the customer and the development work, so that customers can directly drive development.

Development teams (Scrum team)

Mainly responsible for the SOFTWARE product development under the Scrum regulation process, the number of people in the 5~10, each member may be responsible for different technical aspects, but requires that each member must have a strong self-management ability, at the same time have a certain degree of expression; Members can take any form of work, As long as you can reach the goal of Sprint.

Scrum flowchart

//------------------------

Below, we begin to talk about the specific implementation process, but before we speak, I have to explain an English word.

What is a sprint.

Sprint is the meaning of a short distance race, which refers to an iteration, and the cycle of an iteration is 1 months (4 weeks), that is, we want to complete the development of an iteration as quickly as we could, which we call Sprint.

How to develop scrum.

1, we first need to determine a product Backlog (in order to prioritize a list of products), which is responsible for production Owner;

2, the Scrum team based on the Product backlog list, do workload estimates and arrangements;

3. With the Product Backlog list, we need to pick out a story as the goal for this iteration through Sprint planning meeting (Sprint Planning Conference), which has a time period of 1-4 to four weeks, The story is then refined to form a sprint Backlog;

4. Sprint Backlog is done by the scrum team, and each member is subdivided into smaller tasks based on the sprint backlog (the workload for each task is completed within 2 days);

5. During sprint backlog, which is selected during the Scrum team's completion of the planning meeting, you will need to perform daily scrum meeting (day standing meetings), where each meeting is controlled by about 15 minutes, and everyone must speak, and to report to all members in person what you accomplished yesterday, and make a commitment to all members of what you are going to accomplish today, and to meet the problems that can not be solved, and each person will go to the blackboard to update their sprint burn down (Sprint Burndown chart) before they are done.

6, to achieve daily integration, that is, every day to have a successful compilation, and a version that can be demonstrated, many people may not have used the automated daily integration, in fact, TFS has this function, it can support each time a member to check in, automatically get the latest version on the server, and then compile in the server , if you pass then immediately execute unit test code, if all pass, then release this version, when a formal check-in operation is saved to TFS, any failure in the middle, will notify the project manager by mail;

7. When a story completes, that is, the sprint backlog is completed, it means that a sprint is complete, at which point we are srpint Review meeting (Demo conference), also known as the Review Meeting, Both the product owner and the customer are invited (preferably the boss of the company), and each Scrum team member will demonstrate to them the software products they have completed (this meeting is very important and must not be canceled);

8, the final is Sprint retrospective meeting (review meeting), also known as wrap-up meetings, to take a rotating approach, everyone has to speak, summarize and discuss the improvement, put into the next Sprint's product requirements;

Here are some of the scenario diagrams used in the scrum development process:

The above illustration is an example of a Product Backlog.

The picture above is the daily standing meeting, the participants can stand at will, the task Kanban to ensure that everyone see, when everyone has finished speaking, to go to the task version to update their own Burndown chart.

The task-looking version contains unfinished, ongoing, completed work status, assuming you have completed an unfinished job today, you will have to paste the small card from the completed area to the completed area.

Everyone's work progress and completion is open, if a person's job in a certain position for several days, everyone can find his work progress what problem (the number of members preferably 5~7, so that each person can use a special color label paper, At a glance can see from the task version who work fast, who work progress slow)

The image above is not a poker game, it is a planning card, it is to prevent the project in the development process, by some people led.

How to use it. For example, a programmer to develop a function, need 5 hours, B programmers think only need half an hour, then they each take the corresponding cards, hidden in the hands of the final showdown, if the time gap is big, then A and B can discuss a why 5 hours ... Agile development. ZIP (8 MB) Download number of times: 1