Power
As a project manager, you need to be authorized, otherwise you are hard to implement your plan.
Power is mainly from the trust of your boss, get management, evaluation, and reward your membership from the boss.
At the same time, their own expertise, the skills of skills, the style of people, and your own personality charm is the source of power
2. Project Golden Triangle
The first thing to pay attention to is the project gold triangle, consisting of three edges, they are project objectives, resources and time.
What are the purpose of the target - the purpose of the project, how much is the demand for the project, how much software is functional or characteristics, which results are submitted, what kind of quality standards need to meet
Resources - mainly human resources and funds, usually include computer software, hardware, etc.
Time - Completion of the project
You need to put the gold triangle in your heart. When one of them changes, the corresponding adjustments are carried out. For example, the project is completed in advance, you need to reduce some features, or add some people.
3. People with knowledgeable skills
Many projects have failed without people with demand (such as knowledge, software engineering knowledge) and capabilities (such as software planning capabilities). How to recruit qualified people? How to make up for the insufficient knowledge, cultivate people in project work, how to reduce the learning curve (productivity increases with familiarity), get their support, incentives and encourage them.
Establish a harmonious working environment by respecting individuals.
4. Set the target, specify the direction
As a project manager, you need to set the goal and specify the direction. If there is no clear direction, the team members will do nothing, or lost in their daily work. You should always focus on this goal. Like a leader, point to the target, then say: "Come with me".
5. Alent time
The project takes a certain amount of time to operate, and the software development has a certain internal law. The software program is most impressive. On the one hand, it will lead to the project to bring risks to the company; on the other hand, unrealistic plans will bring too much pressure to project members, causing morale to decrease.
So try not to accept Date-Driven project, because you will die very badly. Add a certain buffer buffer (15% - 20%) to deal with uncertainties.
6. Plan, plan, plan
Forewarned is forearmed, without prejudging the waste". If you go to the navigation, you need to get a map, you have your present position on the map (for your current situation), your destination (you are going there), there is also the route reach there (how to do). Like the project, you must first analyze your project scope, estimate software scale and workload, and develop project plans. The main part of the project plan is the work decomposition structure (WBS) and progress. The work decomposition structure is the layer-by-layer decomposition of the task to be completed. Decomposing you can assign tasks to group members, decompose to your control project. . The schedule is the schedule of the task execution, which can set a milestone and checkpoint in the schedule to check the milestone when the project is executed.
Doing a project plan to do a small and small, seize the key links affecting the success or failure of the project, mainly. Key path is the main aspects of the impact project. To analyze key paths, first need to define the dependency of the task, then find a shortest path, ie the key path. A task delay on the key path will be postponed.
As a project manager, it is necessary to have certain self-management capabilities. When working, it is always a plan (PLAN), execute (DO), checking the implementation situation (CHECK), thinking about the plan or execution. Improvement. The so-called PDCA cycle 7. Yue customers
Be familiar with the relevant personnel of our customers, get their own good feelings, and need their support in demand acquisition and subsequent layers.
The purpose of adopting "customer satisfaction first", try to strive for users to participate in the project early, and participate in the project as much as possible.
8. Demand management
Many project problems have emerged in demand, or spread. Undemental demand will lead to many uncertain factors, and cannot guarantee the success of the project.
Therefore, it is necessary to establish a control process for demand changes. Confirm the needs as soon as possible. After the demand is incorporated into the baseline, the change in demand is carried out in accordance with the change process, including affecting analysis, deciding to adopt or increase in the next version.
To make a priority evaluation of the needs. First do the high priority demand, then do the low demand for priority. Select a more certain demand, put ambiguous demand to the back.
Demand documents are the basis for communication. It has established a joint understanding of project groups and customers on demand; and it also establishes project demand personnel, and design, implementation, and testers.
9. Communication
Communicate with the project, communicate with customers (internal customers, external customers), communicate with the project officers, communicating with your team members.
It is necessary to report the status, progress and problems encountered to the initiator. Strive for others to support your project.
If your project is bigger, pay attention to promoting communication between project members to better collaborate in work.
10. Management commitment
Get a commitment is very important. You need your group members to commit the mission for him. At the same time, the team members can choose not to promise a task. Commitment means that in order to complete the task. For project investors, users have to handle their commitments. When the project change is designed to the customer's commitment, you must actively communicate with our customers beforehand.
One promise, you don't want to promise, especially if you think that you think is unrealistic.
11. Team construction
It is difficult to share with your group members in the interests and ideas. At the same time, I went to Happy Happy to celebrate with your team when arriving in the milestone. In addition, arrange some entertainment activities.
Make you not only a work partner, but also a friend who talks in life. Strengthen the identity and belonging of the group.
12. Improve morale
Make the results of their efforts to visualize, after a part of the project is completed, in the project group, inspiring the gas. Being a certain way to make a celebration, encourage each other. Don't shirk responsibility when you encounter difficulties. Good morale will bring you high productivity.
13. Pay attention to risk
Through a risk-driven manner, transitioning the Reactive is transformed into proactive. Risk identification and evaluation in the planning phase, pre-developing priorities in risk incidence and more affected. In the project execution, risks are constantly reassessing, focusing on the risks of the ranking, paying attention to the risk of critical paths.
14. Familiar with technology
At this stage, the project manager is generally the cultivation of technical backbone. In the project, it is necessary to take technical research, leading other people (especially new members) and doing technical decisions.
At this level of the project manager, technical capabilities are mainly based on the ability to control technology.
15. Version management must guarantee
Version management main management work results, helping to stabilize a version that can be released, reducing the chaos in the development. It is guaranteed to construct a newest system version.
16. Recentty
To be pragmatic, it is possible to adapt to the environment, depending on the specific situation, not the various theoretical management projects of software engineering. Applicable is the best. 17. Authorization
You have to learn to share power. When making decisions, please ask the members' opinions and let all people participate. Participation in the sense of motion. But to make a decision, so-called fully expressing, unconditional execution
This is important because they have to grow in the project. Through participatory management, let the team members participate in the decision-making team have been awarded more active teams.
18. Strengthen monitoring
In the project execution, you should monitor the situation, progress, and status of the project. Check and control in milestones and checkpoints.
19. Using the development technology
To understand the development technology you use, estimate the risk of technology, do not easily use technologies that have not yet mastered.
20. Use prototyping method to shorten feedback time
Get feedback from customers as quickly as possible, such as selecting prototypes. When the demand is unclear, or when the design idea has not been verified, the prototype (sub-abandoned and evolutionary type) is quickly established to obtain feedback from the user.
After the technical solution is selected, it immediately starts to establish a prototype, verify the technical solution, and reduce the risk of development.
21. Method for adapting to changes
In the case of allowing, an object-oriented method is used to reduce the coupling type between the modules to accommodate the changes in system requirements.
