Cmme 3 level 1

Level 3 is not a high level. I participated in the Level 3 Activities of the organizational unit. Here I will talk about some of my feelings.

1. Why is the quality of software still not good with software quality assurance. Let's talk about quality.

A has been popular in the industry, whether it is ISO or cmme. The State supports enterprise-level access and even preferential policies, however, many companies or organizations that are too level-1 have not really helped the enterprise's R & D, but have become a burden. Every year, the quality personnel of each organization are busy preparing for the level, project preparation, document preparation, and training for those who have participated in the level. In addition, I beg my grandfather to tell my grandmother that every time I pass the class, it is like a war.

B developers are very disgusted with the level because they have to come up with a lot of resources to cope with the writing of various documents, even if they know that these documents are almost useless, but they have to write for the level. In addition, if there is a time conflict, the project team has to be subject to the delays brought to the project.

C leaders are very unhappy. After passing the level, the quality should go up. Why is the quality still not good? The cost still cannot be lowered. I often hear the boss yell at the quality personnel and the quality cannot go up, what are your quality personnel doing.

These causes are mainly due to the misunderstanding of quality work by senior management, developers, and even quality personnel. Therefore, it is troublesome for yourself and everyone.

The word "quality" is separated by "quality" and "quantity. For an enterprise, it is the quality of a product and the quantity of production.

Let's talk about the number of products produced. We all know that the number of products = production efficiency * production time.

Note that there is a problem here. For Development, the production time should be the effective production time, rather than the general conceptual production time. The production of software has a lot to do with people, people are not machines. If machines are not bad, they can be produced all the time. The actual production time of a developer is greatly affected. The actual production time is very small in his work time. Generally, it is good for an enterprise to have 30%, and about 50% of the good staff, this data can also match with the content of the IT industry. Many developers prefer to work overtime and work at night. Why do we need to work overtime? It's nothing more than less effective time at work, but at night? No one is disturbing, so the work efficiency is relatively high. That is to say, it takes a long time to work in the same time, however, it is the conscious or unconscious behavior of all people.

Why are there so many differences between valid working hours and working hours? Here are some common phenomena.

As a large enterprise, the first waste of work time is a meeting. The meeting is the most two hours of work. Our company once had such a thing: a project was established, A project approval meeting will naturally be held for project initiation. It was originally expected to be held for one hour, with the participation of project managers, developers, senior managers, and administrative and quality personnel, as a result, the project meeting became a run-off meeting or technical seminar. The meeting lasted for four hours. At that time, there were 10 people attending the meeting, and there were 40 people working at the meeting. That is to say, the efficiency of the time and work hours was only 25%. In addition, many people in the meeting only need to be notified and did not participate at all, such as quality and administration and three developers. If these five people are removed, the Meeting efficiency will be 12.5%. How can this be surprising.