Meditation on Agile Development

 

Recently, I saw a friend's blog, which mentioned some typical agile problems.Article
In the discussion (for example: <why agile cannot be successful> http://coolshell.cn/articles/5044.html), here, choose a friend

On his blog, his question (see: http://www.blogjava.net/pengpenglin/archive/2011/06/01/351552.html)
The problem is as follows:

A. Is agility a stand-up meeting? Is it iterative to divide the project into several small stages?
 
B. What is the size of agile teams? 10 or 4 or 5?

C. How do I configure the personnel in the agile team? Is there a level equivalent to experience?

D. Will agile Pair Programming become a fatal defect when there is a short board in the team?

E will the entire functional team and de-angular Team (especially without the PM role) of the agile team make the project out of control?

F. Agility does not completely discard documents, but what level does the document need? What is the difference with traditional documents?

G. How can we ensure that the structure of agile development is flat?

H. What problems do stand-up meetings have if they do not turn into a journal report?

I. What business scenarios are agile development applicable? Project or product? (My peers tend to be projects, saying that products often need to be changed, but agile declarations are not

Are you changing)

J. In Agile development, how does one divide Members? What is horizontal or vertical division?

K. In Agile development and management, How can new users get familiar with products and architectures as soon as possible?

This is a typical question. I will try to answer this question below. There must be something totally different. Please advise:
A. Is agility a stand-up meeting? Is it iterative to divide the project into several small stages?
A: Of course, it is not just a standing meeting. The reason for standing is to try to solve the problem within 15 minutes and be as short as possible,
If there is such an idea, even if everyone is sitting in a meeting, the host is well grasped and agile.
Several small stages may not necessarily be equal to iterations. It depends on whether you have applied XP ideas and methods well in each stage. Otherwise, it is different from the traditional RUP.

What is the size of agile team B? 10 or 4 or 5?
A: Generally, it is very efficient and appropriate for 4-6 people to create an agile group. Because there are many people, it is troublesome to manage and there are many opinions. Of course, if
If your group is composed of agile elites, congratulations, you can do it for 10 people (but don't forget the truth that three monks don't have water to eat), but the problem
Yes. How do you manage these 10 agile elites? Split it into two groups! In addition, if the project scale is small, 2-3 people can be agile,
Do not be metaphysical.

How do I configure the personnel in the C agile team? Is there a level equivalent to experience?
A: In my opinion, if the team is to be closed, the level is really good. Otherwise, the beginner is watching and teaching,
There is no collision or interaction. However, a team does not necessarily require too many people to have agile experience. A small number of people have no agile experience,
Sometimes it is a good thing. The so-called "public" fans, the audience is clear. In addition, pay attention to the fusion of character in staffing so that they can get along well with each other,
This involves interpersonal relationships. At that time, I learned something else.

D. Will agile Pair Programming become a fatal defect when there is a short board in the team?
A: I have always believed that Pair programming should be used with caution, especially in Chinese situations, including the environment, level, and system of Pair programming,
Otherwise, it is possible to become an external obstacle.

E will the entire functional team and de-angular Team (especially without the PM role) of the agile team make the project out of control?

A: Agile Ba, scrum master, and other roles have also assumed some PM roles. Of course, SQA is also responsible for many of them.
Scrum master, which depends on the manpower configuration of each company, or the role of PM can still be used, because it is possible that the scrum master in the team
It may be done by those who are more competent and interested in process improvement, but it is better. PM is still responsible for PM role and Management progress.
In fact, the function is a little different from the traditional PM. It is equivalent to dividing the role of "scrum master" into two.

F. Agility does not completely discard documents, but what level does the document need? What is the difference with traditional documents?
A: Agile document. I think it is enough to say "the team can understand the document when it is used, understand the document correctly during execution, and hand over the document smoothly when it is handed over,
Even inCodeThere are a lot of important documents that can be written, and comments can be upgraded to a level. However, when delivering users, users need a set of traditional documents,
It is necessary to prepare in advance and assign a person to do the work. Therefore, documents must be available.

G. How can we ensure that the structure of agile development is flat?
A: This is a big question. I personally think that no matter what development method, we must implement and strictly enforce the system before,
When the team reaches a consensus, everyone is agile, and their thoughts and objectives are recognized, they will have the motivation to continue working.

H. How do I know what you are doing and what problems do you encounter if you do not want to report on your daily bills?
A: The time is specified. Second, some people record it. The record template should be simple. Do not use traditional meeting-style troublesome record formats;
In strict accordance with scrume, what was done yesterday, what difficulties were encountered, and how to do and solve them today. The Creator touched the bottom one day before
You may be aware of the topic that you want to discuss during a standing meeting. Ideal for every Hitachi Conference

Team members arrive at the office one after another, receive emails, and check the information. The meeting time is up, and the team members come to the whiteboard. Let's say hello first.

Jokes make a lively atmosphere. Then, the team members stood in front of the whiteboard to describe the team's plan and obstacles they encountered yesterday. Relaxed atmosphere,

The teams that have completed the task are praised. The teams that have encountered the obstacles quickly implemented the solutions for those who will be involved in the problem after the meeting. It takes about 6 minutes to complete the meeting.

Enabled. Everyone stood together and "123xx team is the best" was the end of the meeting.

I. What business scenarios are agile development applicable? Project or product? (My peers tend to be projects and say that products often need to be changed, but agile declarations are not enough.

do you want to embrace changes?
A: it should be said that all of them are suitable, but it seems that there are many projects in practice.
J. in Agile development, how does one divide Members? What is horizontal or vertical division?
A: It seems that it is enough to divide by scrum. Make adjustments when necessary, but feel that the product manager still needs to set up this function. Of course,
some can work in a leisurely manner.
K. In Agile development and management, How can new users get familiar with products and architectures as soon as possible?
A: My personal feeling depends on whether a new employee is willing to be agile or not. If you like the tradition in the bones, don't let him join the agile team.
second, we should do a good job in training, improve the team atmosphere, and encourage more. Sometimes we may wish to build a pyramid sales atmosphere. The training should be a mentor system, and old people should bring new people.
allow new people to express their opinions more easily, so that new people can be mentally agile. If you are a newcomer with strong technology, you can set up a
shift quickly, for example, as an observer for requirements, planning, architecture, coding, and testing, to quickly track the entire process, don't think that as soon as you get a new employee,
let them work as their animals.