Process improvement is repeatedly mentioned in many soft materials
It is expected that the goal of CMM did not show the goal of CMM, but some basic management methods can still see the effect in the short term.
Such as conference system, attendance system, project resource unified management, configuration management, test management, etc., the following description:
The meeting system is not a scope of software engineering, but it is one of the basic corporate management systems. If this is not good, it is difficult to imagine that it can huge knowledge system.
Software engineering implementation. A project team, generally have a fixed one week
The case, summarize the work of the week and plan to work next week, designate a host before the meeting
And a recorder, the time cost of the meeting record is relatively small, just pay attention
The conclusions formed by the conference can be recorded. In addition, some meetings should be held every week.
Depending on the specific situation of the project. There are a lot of formats for the meeting record.
It can also be done according to your own requirements, as long as the key content is recorded, it is enough.
Attendance system is especially important for high-tech companies. Most of the employees in software companies are young people. There are more many people who have just got out of school, and the young people are at the time of the project.
Don't worry, but usually have lazy situations, such as late, early retreat, etc., in some new software companies, frequent overtime has become a lot of software engineer works.
This is unfavorable. Should try to minimize overtime, but the usual attendance system must be strictly enforced, can't work hard because someone, a group of works, hard work, hard work
Relax attendance is made. There are a lot of specific ways, and the internal network is a good way.
In a project team, even if the number of people is small, it should also be divided into work, for example, let someone take the task of coding, design and other tasks to tending work, someone
Responsible for configuration management, the team leader is responsible for the unified management of the document, the format specification of the textbook is best to check, the specific content of the text is written by each member, the benefits of doing division of labor are to avoid everyone seems to
Everything is done, but nothing is universal, there may be everyone writing, but the format is different. If everyone is required to write the same text, there are many difficulties, it is better to let one person
To ensure the format of the text, it is usually guaranteed that the text can be updated in every week.
Configuration Management is a comparison of Issue in the CMM and implemented difficulty in implementing difficulty. Generally, it can meet the requirements with SourceSafe, CVS, etc. If you use Microsoft IDE, it is usually used.
SourceSafe, if it is a development environment under jbuilder or Linux, uses CVS. But pay attention to it. Once you have selected a tool, don't give up easily, you must gradually understand the skills of use.
The implementation of test management also requires a certain understanding of the importance of the test and the general theory. This information is a large, nothing more than test classification, steps, etc., and most will
How important cloud clouds with a very heavy pen ink, the importance of testing does not need to say more, everyone has realized. After understanding theory, you are also looking for some tools, such as OpenSource.
Bugzillar is a very good bug management tool. It is just a pile of things such as Apache, Perl when they are configured. Also consider Chinese, and so on.
