Foreword
To better develop software, some software engineering methods and methods must be introduced in the project group. This article discusses some means and methods that a project manager should be able to implement in the project team regardless of the company's circumstances; of course, the company has a more feasible, more ways to choose; here is only the worst Methods can be employed in the case.
This article lists some methods according to each of the simplest waterfall modes, and should be employed in other modes.
Demand phase
The management of demand should be throughout the development process. At this stage, the methods you can use are:
2 CCB (Change Control Committee)
Establishing a CCB (CHANGE CONTROL BOARD) is the premise of demand management, otherwise demand management will become an empty call.
The CCB must include the customer's decision-making person, the project manager, the project manager leaders, key designers, test leaders, SQA., Etc., is suitable for about 5-7 people.
Demand confirmation, changes such as changes must be approved by the CCB.
CCB has the highest power for the entire project (not only responsible for changes, but also important decisions such as project manager report, key intermediate working product reviews)
2 Review, incorporating baseline
The original demand must form a document and is reviewed by the CCB and then incorporates the baseline management. All changes require CCB reviews.
The general step of the review:
1. The project manager puts forward the subject, pointed out that the affected, involved objects, and the impact of assessment (mainly brought about the scale, workload, cost), proposing planned and planned executives, and raising possible risks;
2. CCB to decide whether to agree or require the project manager to modify the above item;
3. After that, the project manager submits the implementation report.
4. Finally, the CCB specifies the representation or verified by SQA.
If it is too small, too many, We will be reviewed.
Project plan
The project plan is a guide or script, in fact, at every stage, it should be re-, small scope will be revised.
2 Select the right software development life cycle
Regarding the choice of life cycle, there will always be a lot of controversy. At present, the most used in China is the life cycle of pure waterfalls; my opinion is: must have a better choice, but this is the safest, least in the actual controversial choice.
The main points for choosing the right life cycle are: There must be a statement of the reason. Be sure.
2 Division stage - small milestones
According to the selected lifecycle model, consider the people who can be invested, the various development phases will come out. The end of each phase must be a milestone. If the milestone exceeds a month, then choose the right point as a small milestone every after a month.
For each milestone, the project manager should submit this stage of work report, which should generally include:
1. Reasons for the statistics and estimates of this phase and their differences
2. Work products completion
3. Demand change statistics
4. Questions and their resolution statistics
5. Summary of the advantages and disadvantages, pointing out the impact on the next step
CCB listened to the report and evaluated this phase.
The small milestone can prevent project out of control, allowing project managers, project groups and management to correctly recognize project progress, and assist project development, strategy, and project visualization; avoid project problems.
2 decide to work products and including intermediate working products
In the most confusing project, work products and intermediate working products are not defined, or can be met, add or remove products. Determine working products and intermediate working products, in order to determine the importance of each product, calculate its workload to enroll enough, suitable personnel to develop it. 2 Project work decomposition
Generally, the system is decomposed into modules or even more thinner. It is necessary to pay more than the project manager or analyst. According to the actual understanding and humanity of the project product; an advice: the fine, doing it, The work will be much easier.
The average person only disks a product. In fact, management should also decompose, and it is more likely to work.
2 estimation
It is estimated that it is often ignored because the estimated results tend to be seriously exceeding the budget, and people are surprising. At the end, the result is often close to the original estimated number.
It is estimated that each stage is performed as part of the update plan, and each new estimate will be more accurate.
It is estimated that experienced people should be selected and should be selected.
The estimated result should be used to guide the planning of the next stage, even if it is not officially acceptable, the project group should not forget these numbers, and the time is used as a reference.
2 Clear responsibilities - team construction
Based on project features and personnel features, the right mode should be selected to form a team to develop, and everyone should have clear responsibilities and work.
Minimum, everyone should have clear responsibilities and work.
2 agreement communication, channels
Establishing communication channels This can be enabled, but it is necessary. Communication channels should be open, smooth. For each person, the leadership, reporting methods, reporting methods, and ways to report the leadership, conditions and methods reported by the report.
It is recommended to carry out project logs, weekly report systems, and specific methods can be referred to PSP, TSP. The main point of the system is that the log is first responsible to himself, cannot be used as a basis for evaluating employees, which is a member "open privacy." If you are required to fill an 8 hours a day, there is no meaning; in fact, in our own project group, according to the log, no one has more than 35 hours per week, and the average is only about 28 hours - of course, You can still see that they are very busy every day, sometimes overtime.
The weekly system is the most feasible software development management means this paper. 1-1.5 hours per week, everyone briefly reports this week's work and next week's work, the problems and difficulties in work, at this time, he will get the recommendations and help of the entire project team; the project manager can confirm Project progressive; team atmosphere is strengthened. If there is still a lot of surplus time, the project team can discuss development technology, skills, and conduct some technical exchanges.
In short, insufficient communication is a big problem in software development, the more serious the big project.
2 agreement development discipline, standardization
No rules, no standards. The project team must have some discipline and cannot be completely reliable.
In this regard, there is company culture, atmospheric, the atmosphere is the best, otherwise some rules should be formulated.
This is also an important part of the team.
As for the development specification, depending on the project, the point is: must be, even if it is not perfect!
Moreover, you should open public and publicized as soon as possible.
2 Risk estimation and preparatory response plan
Risk estimates should be performed at each stage, usually based on risk lists, everyone is estimated.
In fact, everyone fully recognizes the situation and potential difficulties of the project.
This matter, it is always better than it is not good.
2 CCB review project plan
The project plan must be recognized by the CCB conference, otherwise there will be a problem!
design phase
2 Periodic internal reviews and takes out
At this stage, the purpose of periodically internal review and walking is more for communication, check whether the modules can collaborate, have contradictions and omissions, as a strong supplement of ordinary informal communication, everyone can take a long-term supply, brainstorm, a few Personal head is better than a head; the second purpose is quality control. The third purpose is the control progress. According to the above features, the review should naturally adopt a conference method, maybe some people feel lengthy, dragging, wasted some people unnecessary; but this way is very good, it is worthwhile; as for the organizational meeting, generally Project managers should make more brains and mobilize everyone's enthusiasm. Some people will use Checklist's way, my experience is: this way has weakened the communication, and the support of a good system is required, otherwise it is easy to walk form.
2 Project tracking
After the project is planned, the project tracking work begins. Tracking tables should be filled in every week so that problems in the project will be found in time; and it is best not to use Project to track, but make one or find the right software. It is generally developed according to the project plan, with the following content: task package, scale, workload, progress, actual scale, workload, progress, and two errors and cause analysis.
How should the percentage of the task package completed? My standard is: If you just listen to members report, there is no 100% of the completion of 0%. It is the principle of 0-100; listening to members report, I have read the work products, it is 0-50-100 principle; carefully check Over, you can refer to Members' reports, follow the principles of 0-25-50-75-100. If a 5 working day work bag, write 43%, it is not there.
The results of the project tracking are used to analyze the progress of the project, the milestone report, and be sure to be true.
2 change control
The specific means of change control, please refer to the principle of the demand phase. At this stage, it is generally only the need for unreasonable demand, or requires change to design contradictions. Some non-baseline changes do not need to be so strict, meaning that there is no need for a CCB review, but the project manager should decide whether to convene the relevant personnel in the project group according to the actual situation.
At the same time, everyone should develop habits that comply with changes in changes in this stage.
Encoding phase
2 Re-work estimate, there is necessary to revise
Entering the coding phase, the understanding of the project is very clear. According to the design, the number of line lines can be calculated. Retreating the work estimate, can better distribute the personnel to the technical characteristics and interest in the right, improve the enthusiasm of the project team; at the same time, the management can clearly recognize the real situation of project progress, and make the correct decision or avoid avoidance They make mistakes.
2 Standard development and training
The code of the encoding is now gradually gone, but it is still necessary to implement or develop coding standards in the project group.
The unified coding standard can make it easy to assist each other, and communicate, to lay a good foundation for the work, testing and other work.
After the coding standard is developed, we must first conduct training within the project group. However, it is said that it is training, it is better to discuss and unify the premise of the establishment of future enforcement and inspection. (Do not teach it, it is abuse, teachings, it is the same)
2 Periodic Test
According to experience and some statistics, the effect of the take-out is better than the test.
In contrast, unified coding standards is also established in the project group by a unified coding standard. My experience is: At the beginning, arrange 2 times a week, once a week, only one hour of one hour, the focus is the coding standard, followed by bug; everyone can learn the fine style of others, correct I have a shortcoming of myself; the entire project team is basically unified after two weeks. After this, you should focus on the program function, followed by bug. 2 week creation or day creation
2 Project tracking
Project tracking is easier in this stage, because quantified things are more, the virtual thing is less. The basic method is the same as the previous stage. Through tracking, it is already possible to see that the modules are not designed in the previous stage.
Tracking must be analyzed and analyzed that there is a action.
2 change control
At this stage, it is generally the development of some design errors when the developer is implemented; at this time, the project manager is required to strictly control, and the designer and developers are really needed to change, or the implementation is not a meeting designer the purpose. If you need to change, you should carefully study the impact range and evaluate the loss.
In this stage, later, with some products gradually form, the customer will make a change requirement; at this time, it should pay attention to the principle. At the same time, it is necessary to do a good relationship. Of course, the first is the principle -ccb consent.
2 version control
In fact, version control should be expanded when the project is started, but it is not necessary to do all project groups, and it is even more unhappy. However, in the coding phase, it is best to have a version controlled, and a good control mechanism can reduce a lot of unwanted work and even avoid some disasters.
Good version control is not from a good version control tool software, but the system of version change control and thus formed good habits. Establish a stipulate or specification of a text and ensure that it can be implemented to make the version control will not be in the form.
If you have a version control, it is recommended to implement MISRA RULE 10 - Do not residual waste code.
Common version control tools are VSS, CVS, the ClearCase in the Rational Kit is also very good, just not using people who will be configured; when developing under UNIX, it comes with SCCS is also very good.
Test phase
2 formulate rework standards and reaffirm discipline
A bad program is always constantly being modified, most of the test work is caused by a few programs that are completed by several programs or individual programmers. The continuous modified product will not become a good product regardless of how many times.
Therefore, the program rework standard should be formulated, one can refer to the value of 15bug / 1000Line. Directly reached this standard, directly delete the program, requiring programmers to rewrite; the new program reaches this standard again, change people. Moreover, this provision should be strictly implemented - the premise is that this rule notifies everyone in the coding phase.
2 day creation
The day creation of the test phase is simply forced, especially in the early days; otherwise the test is not going on.
However, pay attention to not losing the principle, and the version control is destroyed in order to drive.
2 change control
The test phase is the most important time, pay attention to the principle, and to adhere to the CCB review. The necessary changes are required, but it is necessary to carefully evaluate its impact. Changes in a hurry have both destroyed the rules and often destroyed the product. Remember a famous saying: If the chef is long, it is because he wants to make the dishes better.
2 version control
If there is no good version control action at this stage, the test work will definitely feel; and this is the premise of day creation.
2 Project tracking
Project tracking is most difficult at this stage. Because things are often trivial and intertwined together. The project manager is both by the referee, but also branches, but also to go in person when the coach, the captain is necessary. A good product, will not be a mess in the test phase. However, it is necessary to adhere to the project tracking; accumulate data from this stage, in order to true evaluation projects, each member of the project group, the technology (including management technology) adoption, for the company, personal accumulation experience. So, although the project manager is very busy, it is very tired, there are many important things to handle, but it should still adhere to the project tracking.
Project end
Project summary should be conducted when the project is finished, mainly to evaluate project products, the technology, management methods, advantages, disadvantages, and each member of the project group.
The data obtained by project tracking can be used as the basis for evaluation, but cannot be quantified as a quantitative assessment (grading or score), which can only be qualitative evaluation - a detailed text description. The summary purpose is to face new projects, rather than disciplinary, quantitative evaluations, for the next new task, there is basically no help.
How can I correctly evaluate and use people, still a management puzzle.
Welcome: huangjien@163.net
