This article www.javaeye.com forum One of the long text "What did CMM bring us?"
I saw everyone about the discussion of CMM, I feel very touching, I also published some opinions here.
Personal background-2004 Singapore National University graduated, now a local company (CMMI-4) work, work experience 8 months, the qualifications are Shangshang.
Team Background - Project Manager, experience more than ten years, three four-year work experience in Project Leader. Leader a is responsible for document management (librarian, business logic negotiation, and all databases related to DB Design & Data Migration). Leader B is responsible for architectural design, system integration, and all Security related processing. Leader C is responsible for writing a recovering code across projects, and Leader B is responsible for all technical related matters, including me, including me, average work experience, said average because people are very Fast, come and go very unstable
Project Background - This is a webapp. Team management basics follow the CMM specification, the project from Requirement Gathering to the delivery as a year, the original design to give China branch, and later can't drive the progress, more internal Testing negative feedback more In the case of change to half the outsourcing of half, the quality of the last outsourcing is still not, when the project progress cannot be guaranteed, Singapore headquarters undertake the UAT and final system test and debug tasks of the outsourcing. Project has about 50-100,000 new yuan
Project progress table - NOV2003-MAR2004 3-4 months demand collection, a series of simulated interface design, customers are signed after identifying demand and seeing interface prototypes, this stage tells the Mar2004-APR2004 1-2 month branch to start writing Code, concrete situation, I know that the APR2004-JUN2004 half task is recovered by the headquarters, starting to drive JUN2004-AUG2004 Branch no longer responsible for code writing and debugging, rushing to the highest peak, almost overtime AUG2004-Oct2004 programming After the task is over, the system test begins, and it has been done in the three months OCT2004-Now zero straw, uat, training, compatibility test, commissioning optimization, etc. . .
Project Status - In such a rapidly flowing company, the project is basically close to the end of the project in the case of outsourcing, without delaying too much time. Although everyone is basically every day to at least 11 o'clock in the evening in July. ==============
LUCIFER issued a question at the beginning, "Is it more than a factor in the documentation and process?" I think the idea of modern software project is surrounded by people. This is not enough, emphasizing the process is because people will make mistakes, they will not know unfamiliar, and there is a normally follow template to provide a timely discovery opportunity. And provide recommendations for correcting errors or rescue projects. The ultimate executor of these behaviors is still a person, so I think that CMM is not wrong, CMM requires a good purpose of writing a lot of documents. It is also clear that it is naturally implemented in the project. Difference, but its core value is not movable. In fact, in other ways, you can learn from CMM's norms. Unfortunately, many companies mention that CMM will only be switched on the document, and I personally feel very unfortunately. For some netizens say that CMM is only suitable for outsourcing, I don't quite understand the reason, I think it should be restricted to the CMM on Mindset. Distance, through SCEA's study, I met a domestic friend, and we often exchange in project management, according to him, talk to customers only to the UserCase level, up to the Module level, afterwards The team began architecture design and programming debugging. The customer will propose / improve the demand from time to time during this process. It is natural, there is a considerable proportion of code to rewrite, and finally there is little item completed on time. Conversely, in my company, the company and customers have a completely different demand acquisition process, and a considerable detailed business logic and interface design are repeatedly discussed in the first phase until confirmed, the customer is signed, and then the real design programming begins. All meetings have recorded and copied both sides so that they have evidence when they are arguing, which is conducive to the progress and resource management of the project team. On the other hand, the progress of delay project has a very high price, which also guarantees the interests of our customers. Because all the processes have, all contracts have recorded the responsibility and obligations of both parties (customers can't arbitrarily add demand, we can't pay free of charge), related documents (basically CMM) It is an indispensable part of the project. Money is the key! No money, no talk, isnt it? Write this, I think if some companies are experiencing the experience of my friend, then a lot of CMM documents does appear unnecessary, but lacking these documents Support, the maintenance of the project and the context of the established Scope will become unpredictable, and do not mention how to control progress and expenditure.
I have recently been in the last lesson. Teacher from the UK, he said that in the large project (European defense intelligence system), the proportion of MANGEMENT has 50-60%, how to coordinate all kinds of resources, including Human capital time, including how to control the progress of the project, is not a simple matter. What I want to say is that even this billion billion pound is not a place that it is difficult to control, and what they need is the idea of Identify IT, Control IT advocated by CMM. Perhaps 5 people's small projects don't have to use CMM, but if we don't engrave CMM's concept in your brain, I use XP and I can't guarantee the final success of the project.
I agree with such a point of view, CMM's point of view ensures that the project runs on the correct orbit, and ensures that a software company has been working in a long time. Many concepts can be used to measure the effect of a project, Defect Rate, Man-Day Cost Per module, etc., which will provide a direction as a matter of important indicators. Don't say that every item is different, so Measurement is useless. I think it is exactly the same, each project has its characteristics, also have a commonality, and the commonality of the management level provides a continuity of the measurement of the metrics. These data are precious, and a small company that has never implemented similar norms cannot be owned. From the document, the template for successful projects is really important. I have many subsequent projects around me soon. It is better than the help of these templates to a certain extent. Dlee said "The center of software development is never process, but there is a creative person itself." As a developer, I saw this sentence very excited, I agree, but this sentence can also improve this sentence. a bit. Software development itself does not necessarily represent the only value core of a project. It is the correct process to gather those who have creative people to create profits. Perhaps it is a very good programming in this regard, which makes it praised, but it is really in almost all multinational companies, there is no life pulse to maintain your own IT department, which is from another aspect. The unsubstituted value of CMM.
Dlee also said, "It is indeed a lot of development in XP mode. It is difficult to find any excuse to take responsibility should be borne. And do more opportunities to develop a paste in CMM mode." The sentence is very interesting, I want to talk about me around me, simply, they are very dedicated! People who are responsible for writing uat plan, I spent a week, I wrote a PLAN of the Pallet, and the papayer is a real guy; there is also a responsibility of Testing, you will carefully record the bug every time; and some people are responsible for system integration, Repeated testing, there is no complaint; I think this is very important as a programmer, I am afraid that our Chinese programmers can do this less, face lengthy documents, we may be more Complament or discard it, even if the update document is not as spessing during imagination.
Finally, I will conclude my point of view. 1 CMM emphasizes Process Control's point of view is very important and there is no longer 2 cmm is lightweight or heavyweight depends on how you use it 3 different countries' cultural and thinking. The deviation of CMM understands 4 CMM is good for projects. It is only 5 people and processes for organizational companies. There is only 6 people - Quality - Professionalism - Work attitude!
Everyone will take a brick, and the little don't mind. Also welcome everyone to visit my blog (not often updated)
I hope to discuss software engineering, SCEA certification (in test), please add QQ 2387763 (indicate SE / CMM / SCEA, etc.) Interested with me * long-term * exchange IT related information and make friends with MSN Smallfox33 @ Hotmail .com
