I believe many people have seen the three songs of "Raising Broad", and it is estimated that many people have seen its tidbits. The tip of the tidbits is longer than the front, I remember it for a long time for a long time. The tibut is described in detail in the form of a record, which covers a number of visual effects, influence effects, trick production, and more.
Making a lot of time an interview with the heads of all aspects, describing the responsibilities they assume, as well as the difficulties encountered during the production process, overcoming the means used by difficulties. Of course, Sprilberg has a detailed depiction of the production. In my opinion, this is a teamwork of Live Tutorial. I recommend him to many friends, suggest PM or Team Leader to take a look.
Many times I will get out or escape from the IT field to find a way to solve the problems I have encountered. Most of these issues are concentrated in people's awareness, and more precisely. Exaggerated, there is no such thing as this field is absolutely wrong, and it seems to be completely opposite two sides to coexist. Hero fast knife in the movie solves the problem of abnormal problems can only appear in the movie. And the most used methods I have been folded. This kind of fold is not acting as a matters, and the two sides say that it is definitely a work deeds.
In a project (medium size, 14 people) I have encountered a problem: Item Group member is not aunt for using XP or RUP. At that time, I didn't know how XP, and RUP understood more. Most members have experience in at least two years, and the two sides have a word, and they are not allowed to make each other. I have been carefully observed, I found that I insisted that I have an application experience in the previous project, and I insisted that I didn't have Real World experience, but they had a understanding of Hello World, but it seems that they are more enthusiastic. How to persuade everyone and make unanimous to me is too difficult. I later thought about a very popular approach - three question.
Because I know more to RUP, I tend to RUP, but I have not exposed. When you call everyone, discuss this three questions:
1. What is the software process? ---- Enhance Communication Promotion Collaboration
2, XP and RUP's respective advantages and disadvantages. ---- former the former emphasizes productivity, the latter emphasizes continuity
3, for our applicability. ---- No matter or wrong, we need to use it for us.
After discussion, the opinions are consistent, requiring the right document, using RUP, but to improve the method suitable for our. It is relatively good results, and I summed up the so-called "three question" at the end of the project. From this, I will ask three questions when I consider the problem, and I have been called three.
The software process was selected, in fact, the participant's responsibilities were basically determined. Up (not RUP) is well done well, detailing the responsibilities of participating roles, emphasizing the division of labor within the team. The development of society leads to the inevitability of division of labor, and the software process is also experiencing such evolution and is constantly refining. Very intuitive role is a variety of roles in the development team, including art, page editing, programmers, warranty, DBA, SA, BA, etc. Everyone's responsibilities are clear. This is the duty, I don't want the programmer to do DBA things (so I use IBATII instead of hibernate).
As the saying goes, "the head, the owner", and the team's development is especially important. The most fear is that the task is not clear, and the responsible person can be found. There is no problem with problems, it is more likely to solve it forever.
Although it has a good division of labor, if a guy is can't live, it is also an annoying thing. A guy was very happy to write a C code for 3 days and in line with our new framework for three weeks. Fortunately, it is not a trunk work item. There is little influence on the influence, otherwise my sink has to add a pen. Many times, if a work item is more than 3 weeks, how can I only listen to my life? What I have encountered, I have a new work item in each person at that time, I have stimulated his enthusiasm, and he also caused him to abandon unfinished work items.
Every time, I have a poor to tell everyone that their responsibilities must be done with their best efforts, at least not to bring themselves. Because, my principle is that any work item is only responsible for one person unless he left. This has some mandatory, nor very science, but this is helpless. Later, I started to do my best to do my best, and I tried to divide the single work within 3 weeks (it), trying to improve the enthusiasm of everyone, but it seems that it is still very depressed.
In fact, each of us can take all our participants to press ourselves. Everyone should have a goal of struggle. These goals should be completed by themselves. Some tasks accepted by work may have conflicts with these goals, but work is not abandoned, at least for most people, the most important thing is to solve this contradictory relationship. Hey, always seize the main contradiction.
The road is long and the road is long, I will go up and down.
