Several understandings of software project management

Since joining the work in 2007, there have been several projects, but they have been involved in the role of project members and have never been involved in a project manager role. China has an old saying that "onlooker sees most", different from the angle of the same problem station, may form different conclusions. Here I would like a general project members of the perspective of the project management of several views, I hope you give correct.

1. Team members choose to be cautious, choose the right people, and when selecting team members, focus on factors such as teamwork, coding readability, competency, and matching of the project.

2. Project vision of the project initial project managers need to negotiate with senior and client, set the project's vision (i.e. the purpose of the project, the overall function to be achieved, etc.), the vision will not be too long and thin, but must have, good vision is like a lighthouse in the sea, so that the project team will not be lost in the project process.

3. The Project plan project plan is one of the most important documents of the project, need to be developed by the project manager according to the actual situation, it is necessary to note that the project plan is not always constant, the project plan is a gradual process from coarse to fine, from big to small, it needs to be continuously refined and adjusted throughout the project cycle.

4. The requirement phase is collected according to the company's direction requirements by the personnel responsible for the requirements, and the requirements are defined to form the document, and then by the project team personnel to design. As a project manager must be involved in this process as early as possible, the sooner the better, the demand collection process can be based on the needs of personnel, project manager supplemented by the model, by the requirements of personnel responsible for collecting requirements and in the form of demand use cases, by the project manager review and organization requirements review, only after the requirements review, The requirements collection process can be phased out.

5. When the project framework selection and construction requirements are determined, the project manager needs to define the framework and the technology used for the project if the customer does not have a clear request. Sometimes this process can be done by the project manager and the technical backbone in the project team.

6. The design phase by the project manager and the technical backbone to complete the project's overall design and design review, and then the design of the various sub-modules can be assigned to specific members of the design, by the project manager and the technical backbone of the audit; it can be done by the project manager and the technical backbone, but the design documentation must be done by a single The project manager is usually the best candidate, one can maintain the consistency of the document writing style, two can ensure that the project team can understand the detailed design of the whole project, from the overall, three can save the project members time, let it focus on the implementation.

7. When the implementation stage enters the realization stage, the project manager needs to control the aspect mainly has the code quality control, the progress control control and so on, the code quality may through the code checks, the review, formulates the code check-in rule and so on the control, the progress may through examines the progress table to control, It is important to note that project managers are always ready to help project members solve the challenges they encounter, both technical and non-technical.

8. After the test phase requirements document is determined, it is necessary to negotiate with the test group to prepare the test case and submit the approximate time required for the test. Subsequent reviews, such as design audits, ensure that the Test team must be involved because the testers and QA staff are more able to identify the review issue.

9. After implementing the implementation phase, the project will encounter more problems, many of which are not technical aspects, but the customer management system, customer site environment. As a result of long-term development phase of the project members are more tired and in the implementation phase of the problem is more, so the project members in morale and mood is prone to instability, then need project manager to control, to stabilize the mood of the project members, improve morale, and more and customer communication to solve the problems found.

10. Technical testing If the project is a type that has not been previously done, a technical test is required to verify that the selected technology is feasible, and technical testing requires that technical testing must simulate the actual environment of the end user and not be tested in the development environment.

11. Check-in control and progress control the project manager must ensure that every day a suitable time period is used to check the quality of the code that the project members check in (including functional correctness and normative, etc.) and the completion of the task, found that the problem should be resolved in a timely manner.

12. Task allocation task allocation should be small not large, generally speaking, the allocation cycle can be a cycle of one week, in assigning tasks to members need to be affirmed, can not be hard to assign tasks. You can refer to the XP task assignment method.

13. Positioning problems The project manager must first understand his position, understand that he is a hub, to play the role of lubricating oil, to deal with the relationship between the project's related parties. The project manager is not necessarily the project team in the technical and managerial skills of the most powerful person, but must be the project team most will deal with interpersonal relationships, all management issues in the final analysis is the human problem, the relationship between people to deal with, project management succeeded more than half, "will do the people let him do, will not do the people teach him to do, Unwilling to do the people urging him to do. "

14. The development of the project specification as the project manager is the head of the project, some of the project's basic specifications need to be developed by the project manager, such as the Project Code specification (can be modified on the basis of the company code specification), Project communication mechanism (how long is the project meeting?) in what form? How do I respond to a problem when the project is in progress?) such as

15. The application of rights as a project manager, in the project has more rights than other team members, the right to exercise more opportunities, but the project manager must be reasonable use of their rights, the right to exercise improper to harm the atmosphere of the team, affect the effectiveness of the team. There are two points to note when exercising the right,

1) To use more influence, less use of the Organization-given rights, influence refers to themselves through the ordinary person, through their own job qualifications and problem-solving ability to earn, sometimes a common team members whose influence will be greater than the project manager, and organization-based rights are vested in the Articles of Incorporation, In the project team, the project manager must be the most organization-endowed right. Multi-use impact less use of organization-given rights can be more flexible management project team, do not feel overbearing, do not cause resentment, the cohesion of team members is more beneficial. But do not hesitate when encountering non-application organization-given rights, and be sure to understand that organizational empowerment is a way to solve problems, but with less priority than influence.

2) do not consider themselves, some project managers think they just work, and ordinary project members of the only difference is only their own to do more, this is a very wrong understanding, if there is such a knowledge can not be reasonable to exercise their rights, can not play a pivotal role.

16. Monthly evaluation of the application company rules the project manager to the project members to determine the performance of the project members per month pay, which is equal to the project manager a double-edged sword, the application of good can improve team morale, the application of the bad will not only harm the team morale will also increase the project cost. The following points need to be taken into consideration when evaluating the month:

1) The evaluation rules in advance declaration, at the beginning of the project will need to work with team members to develop a simple evaluation of the rules, the rules should not be arbitrary, to listen to the views of the team members. Rule-making can include factors such as attendance, code quality, code specification, task completion, and the availability of tools to save team time.

2) The evaluation should be reasonable and fair. Can not be rated according to personal preferences, nor can all play high points, according to the evaluation of the rules of reasonable grading.

17. Overtime treatment overtime is the last resort, should be cautious use, if forced to work overtime must not be done to make arrangements, to first apply overtime, to coordinate overtime, to determine the overtime required to complete the task and check the completion of the task. Another argument about overtime is that if a milestone in the project is done through a lot of overtime, then the next milestone will certainly be postponed, and I personally think it makes sense.

18. Business travel processing company developers mostly in Jinan and the project is Dongying, which requires the project members to travel frequently, this is not a change of fact, but long-time travel will affect team morale and efficiency, will also increase the cost of the project. This requires the project manager to pay more attention to the impact of travel on the project, to reasonable arrangements for travel personnel and cycle, if some team members travel longer, need to pay attention to the long travel whether to make its "backyard instability", if necessary, can come forward to help solve.

19. Project management project Manager is the overall responsibility of the project, and is the chief of the project. The project manager should do the service for the project team, don't let the daily chores harass the team, and the trivia of the team members must be out of the team.

20. The responsibility of the project manager is the overall responsibility of the project, so be sure to take responsibility for the project, when the project can be completed successfully, to understand that this is the result of project team cooperation is not self-completed, and the project team to share the credit. When the project is not successful, you must understand that you are the most responsible person. Also learn to take responsibility for project members, and when a project member makes a mistake, the project manager needs to learn to accept criticism from outside and to protect the project members appropriately.

Several understandings of software project management