3721 of Software Development Project Management

1. Power
As a project manager, you need to be authorized; otherwise, it is difficult for you to implement your plan.
The power mainly comes from the trust of your boss. You can manage, evaluate, and reward your team members from your boss.

At the same time, your expertise, skills, knowledge, style, and personality charm are all sources of power.

2. Golden Triangle of the project
The project focuses on the golden triangle of the project, which consists of three sides, which are the project's objectives, resources, and time.

Goals-what are the objectives of the project, how much the project needs, how many software functions or features, what results are submitted, and what quality standards are required
Resources-mainly human resources and funds, usually including computer software and hardware.
Time -- the time when the project is completed

You need to always put the golden triangle in your mind. When one of the sides changes, other sides will be adjusted accordingly. For example, if the project is completed ahead of schedule, you need to reduce some features or increase manpower.

3. Persons with knowledge and skills
Many projects fail if they do not have the required knowledge (such as business knowledge, software engineering knowledge) and capabilities (such as software planning capabilities. How to recruit qualified persons? How to make up for the lack of knowledge through training, train people in project work, how to lower the learning curve (productivity increases with familiarity), get their support, motivate and inspire them.

Establish a harmonious working environment by respecting individuals.

4. Set the target and specify the direction
As a project manager, you need to set goals and specify directions. If there is no clear direction, the team members will do nothing or get lost in their daily work. You should always focus on this target. Point to the target, as a leader, and then say, "Come with me ".

5. Ample time
The project requires a certain amount of time to operate, and software development also has certain internal rules. Software plans should not be unrealistic. On the one hand, it will lead to project delays and bring risks to the company; on the other hand, unrealistic plans will put too much pressure on project members, resulting in lower morale.

Therefore, try not to accept the date-driven project, because you will die badly. Add a buffer (15% -- 20%) to the scheduled completion time to deal with uncertain factors.

6. plan, plan, plan
Everything is "pre-established, not pre-abolished ". If you go sailing, you need to get a map with your current location on the map (understanding your current situation), your destination (where you are going) there is also a route to get there (how to do it ). The same is true for projects. First, you need to analyze the scope of your projects, estimate the software scale and workload, and then develop a project plan. The main part of the project plan is the work breakdown structure (WBS) and progress. The work breakdown structure is the layer-by-layer decomposition of the tasks to be completed by the project. After the decomposition, you can assign the tasks to the team members, break down until you can control the project progress. Progress is the schedule of task execution. You can set milestones and checkpoints in progress to check the completion of milestones during project execution.

To make a project plan, we must focus on the key aspects and main aspects that affect the success or failure of the project. The key path is the main aspect that affects the project. To analyze the key path, you must first define the task dependency and then find a shortest path, that is, the Key Path. If a task on the critical path is postponed, the project will be postponed.

As a project manager, you must have a certain degree of self-management ability. At work, you always make plans, do, and check the execution of plans ), think about and improve problems in plan or execution ). The so-called PDCA Cycle

7. Please customers
Be familiar with the customer's related personnel as much as possible, get their favor, and need their support in the demand acquisition and subsequent processes.

We adopt the principle of "Customer Satisfaction first" and strive to engage users in the project as early as possible and participate in the project as much as possible.

8. Requirement Management
Many project problems occur when the demand is not confirmed or the demand spreads. Uncertain requirements may lead to many uncertain factors, and project success cannot be guaranteed.

Therefore, we need to establish a control process for demand changes. Confirm the requirement with the user as soon as possible. After a requirement is included in the baseline, changes to the requirement are carried out according to the change process, including impact analysis, adoption or addition in the next version.

The requirements must be prioritized. First, high-priority requirements, and then low-priority requirements. Select a more specific requirement, and put vague requirements at the end.

The requirement document is the basis for communication. It establishes a common understanding of the requirements of the project team and the customer. It also establishes a common understanding of the project requirement personnel, design, implementation, and testing personnel.

9. Communication
Communicate with the project sponsor, customers (internal customers and external customers), project stakeholders, and your team members.
Periodically report the project status, progress, and problems to the initiators. Win support from others for your project.

If your project is large, be sure to promote communication between project members to facilitate collaboration at work.

10. Management commitment
It is very important to obtain the commitment. You need your team members to make a commitment to the tasks they undertake. At the same time, the Team members can choose not to commit a task. Commitment means that you are fully engaged to complete the task. The user must also handle the commitment of the Project contributor. When the project change design is committed to the customer, it is necessary to actively communicate with the customer beforehand.

Don't promise yourself, especially those that you think are unrealistic.

11. Team building
You can reach an agreement with your team members in terms of interests and ideas. At the same time, we will celebrate with your team members at the milestone. Schedule some entertainment activities after work.

So that you are not only a work partner, but also friends in your life. Enhance the group's sense of identity and sense of belonging.

12. Boost morale
Visualize the results of their efforts. After a certain part of the project is completed, the project team will send a message to boost morale. To make some progress, we must celebrate and encourage each other. Do not shirk responsibility when encountering difficulties. Good morale will bring you high productivity.

13. Pay attention to risks
The risk-driven method is used to convert the reactive method to proactive. Conducts risk identification and evaluation in the planning phase, and develops a plan in advance with a high probability and impact on risk occurrence. During project execution, risks are constantly re-evaluated, top risks are concerned, and risks on key paths are concerned.

14. Familiar with technology
At present, project managers in China are generally trained by the technical backbone. In the project, we will undertake technical research, lead other people (especially new members) and make technical decisions.

At the project manager level, technical capabilities are mainly manifested in the ability to control technology.

15. Ensure Version Management
Major version management achievements help to stabilize a version that can be released and reduce confusion in development. Make sure that you can build the latest system version.

16. Sense of presence
We must be pragmatic and be able to adapt to the environment and manage projects according to the specific circumstances of the project, rather than the various theories of software engineering. Which is best.

17. Authorization
You must learn to share power. When making a decision, ask for comments from the team members and let everyone participate. Participation will motivate you. However, to make a decision, the so-called full expression, unconditional execution

It is important that your team members have the opportunity to exercise in the project because they also need to grow. Through participatory management, members can be more proactive in making decisions.

18. Enhanced monitoring
During project execution, you must monitor the project execution status, progress, and status. Checks and controls milestones and checkpoints.

19. Use development techniques
You need to understand the development technology you are using, estimate the risks of the technology, and do not use the technology that you have not mastered easily.

20. Use the original method to shorten the feedback time
Get feedback from customers as quickly as possible, such as choosing the original method. When the requirements are unclear or the design ideas are not yet verified, quickly build a requirement prototype (discard type and evolutionary type) to obtain user feedback.
After the technical solution is selected, establish a prototype immediately to verify the technical solution and reduce the development risk.

21. adapt to changes
When allowed, the object-oriented method is used to reduce the coupling between modules to adapt to the changes in system requirements.