I wrote a lot before, talking about talking people, actually chatting, now look back, look at childish. I have a part-time job in the project, that is, Daily Build. This seemingly simple, but for the Solution I have hung up more than 20 projects, the daily compilation has to be a big problem, especially Microsoft's broken IDE, really I fu le you. It has now developed Buildit, but also half a tool. However, some people often don't consciously, and the time does not take the code Check IN, each time you have to compile 3, 4 times can complete the task. Sometimes I want to smoke him, I really don't understand, why do you have a good thing to do with a dual loss? This is actually a big problem in management, especially in teamwork, what should everyone do? We usually require project experience, industry experience, and so on when recruiting. In fact, it is not that he is proficient in which something is, but in general, today's software development looks like it. I mention that person above. . . Emily, one is that I will enter the company with him, my personal impression is very good, why? After it entered the company, I didn't ask about what technology. A business, such as a business, but asked very well: Can you first give me the following? I immediately made a tribute, secretly led the thumbs, stop A (even love to evaluate the book, the teacher is often used). This is called a master, this is called a professional player. On the contrary, the person who didn't move the blunder, I now asked him to see the norm, did he reply to the standard? Hey, one of the five major responsibilities of the project manager is "recruitment", I will talk later. For individuals, the specification is to say coding specifications (reference rules, naming uniforms), design specifications (symbolic uniform, tool consistency), etc. From the level of software development project, I personally feel that the process is most important. At present, the mainstream is RUP. In fact, it is a series of highest realm, which also contains two front processes of PSP, TSP. TSP must be premise with PSP as a must, I personally think TSP should also be the RUP must be selected. I have the most impressive is the Process Script concept proposed in TSP. Because the TSP repeatedly emphasizes a concept OperationAl. Is the operationability of the process. This may be unnecessary for experienced people, but for some newers, or those who have lacks a running in each other, it is a rare guided material. If you have a problem, there is a very clear manual to tell you how to do it, it should be a rapid thing. This concept is a bit like "big M method set", but it is more simplified than him to simplify, more practical, which is mainly based on company level, and write a few hundred pages. TSP Script needs to be accurate to a few days, each discussion, what ideas are reached, very specific. In such a process, everyone is relaxed.
Let's talk about RUP. I am impressive from just the big four, I started watching it, anyway, I don't understand, I have three core concepts. Now look back at the book 3 times, every time there is different gains, especially the progress of the combination of the project, I found that it is really reasonable (I know that my opinion is not important). I feel that the deepest is that this U is unified. This word should be the core adjective, the essence is also the most headache of all projects. Each concept does not explain from this U. To be unified, you must first use USE Case Driven. We do demand analysis, design, and have a coding. This will be traced back to a USE CASE. Especially when making changes. For example, the customer wants to remove the function of a button, and our RD picks up the phone, and deletes this button, more simple. But if you trace it back, you will not be unified with this USE CASE. This u is not reflected. This example is not good, you are thinking about it. . . . . I personally always "unified" is a good understanding of the management goal that is very good, it is difficult to implement. And not to say that the high unity of the running combination, single is a uniform unity is already difficult. Everyone has a personality, especially programmers, and remember that the CFRONT team said that the management programmer is like grazing a group of proud cats. Yes, these special people who are heavy in technology, who can ignore advanced technologies to personal impact in technology updates, who don't want to use new and better things in the project. On the contrary, from the management perspective, the more mature things are more popular, and no one can't afford. Look, the project may not start yet, Management Goal and Tech Goal are already inconsistent, you say how the entire Baseline may gather, most of them are parallel, all busy. These are all management contradictions, and the project manager needs high coordination skills, peace management and weights of technological innovation. RUP handles this problem and is an "iteration" way. Let me talk about what I encountered, I found that since RUP invented the iteration concept and was widely accepted by the industry, the nightmare of our RD started. It iterated became an irresponsible synonym. Whenever I put a doubtfulness in the SPEC, I always hear such a sound, I have never thought about it, you will first. At first we still hold an understanding attitude, but I found that the two modules in my hand have been released, all asked to re-establish. If it is too expensive, I really want to rush to the headquarters. In fact, my individual's appearance has always been in the emotions of both welcome. Welcome is because he makes up for individual or technical immature, which is similar to the technical immature, which is similar to the good management we often makes up for the shortcomings of technology, but the technical strength absolutely compensate for the defects of management. So why confirmed? Very simple, we are all half-maturing technicians, no one wants your code, your design is not moving back. If you encounter it, you will tell you that you have made great contributions to the project, and you will not talk to the smoke. The same time is the same, iterations over and over again, rarely bring personal or organizational breakthroughs, just managing success, so from a relatively private point of view, I don't like iteration, just like everyone Like Write instead of Maintain. Talk about iteration. From the RUP process framework, it is preferred in the framework. What is a framework? It is simply that a system exhibits features and behaviors. The relationship between his and demand is the relationship between chicken eggs or egg growth. This metaphor is actually very classic, why? Because iterative emphasizes the overall evolution, not local relationship. A time iteration makes your project's framework more excellent.
