Plan your project and show off your project --- the cultivation of Project Management

First Acquisition Theory

(1) What is a project manager?
The person in charge of clearly explaining the meaning of completion to the team and leading the team to complete the project means that the product meets the requirements of the organization for this product and can also meet the needs of customers to use this product.
(2) early project planning
Project planning template:
1. Why does the company develop this product? What benefits does it bring to the company?
2. Review history versions
3. Release Conditions list a series of deliverables of a project
4 goals
5. project organization describes the assignment of responsibilities of the team in the project
6. The calendar overview marks major milestones and what people can get from this milestone
7 Staffing
8. Suggested calendar burnout diagram Gantt Chart
9 risk list: risk no. Risk Description occurrence probability severity exposure degree Response Time Response Plan

(3) Objectives
1. Product goals
2 project goals: Performance Standards and Defect Reduction Goals
3. Team Goals: high degree of automation
4. Organizational goals: improve agility and reduce development time
(4) ensure that the release conditions meet the SMART principle
Ubiquitous SMART determines measurable and achievable relevant traceable
(5) Estimation
Many knowledge workers, especially technicians, have never learned how to estimate. Even those who have tried to estimate, they are too optimistic and always estimate the workload required for a task too low.
(6) how to control the project
1. Take control of the project's pace, like music, football, and Combat Games
2. mid-stage review
3. Sort requests
4. Use a time box to limit the demand for photo exposure
5. Limit iteration to four weeks or less
6. Create a cross-functional team: work together with test and development products
7. Select the lifecycle model based on project risks
8. maintain reasonable working hours: people can complete up to six hours of technical work every day.
9. Manage defects from the beginning of the project
(7) Project meteorological report
1. Sunday projects are all normal
2. There are a few minor issues with the cloud volume schedule, but they can be implemented on schedule.
3. If there is a problem with the Multi-cloud agenda, it can be implemented on schedule through extra efforts.
4. The current calendar or function set has a high risk.
5. Currently, it is difficult to complete the RAIN project as planned or implement all functions.
6. In any case, we cannot fulfill the project schedule or implement the desired function set.

2. Current work shortage
1. Lack of milestones
Although the project cycle is not long, the middle stage does not carry out the mid-term summary, the mid-term exam, there is no milestone
2. Insufficient emphasis on the number of defects
After the development is completed, how many defects are caused and how many defects are fixed? Insufficient use of jira
3. Number of features
How many features are there in this project and how many new features are added during development? I cannot understand myself
4. Do product release conditions meet the SMART principle?
It is not measured in this aspect, but the input and output are as expected.
5. There is no classification for the Extension Project and no early discovery
Severity of Delay

3. What I want to do
1. jira should be well used, learn from the anti-virus team, and solve the defects in different levels, so as to ensure that there are no serious defects during the release.
2. Draw a project speed chart, similar to a scrum burnout chart, but the number of functions may increase over the project
3. How to influence others
The problem is not solved by myself.
Think about the value I can bring to the Organization
What's in it for me ?) Find everyone's incentive factors, raise salary, learn new knowledge, and improve self and team management capabilities. if this person has no incentive factors? Why?
Listening to the team, you must understand the work of others. This is what I have not invested in (I have many tasks and are lazy)
4. clearly understand the project progress, project status, project function output, and the development code of Members when necessary
5. Complete the project documents, hold meetings, determine project milestones, evaluate the construction period reasonably, and complete the work within the acceptable time range.

Thank you for choosing this infoQ mini-e-book. I have not spent any money on the paper version. Let's take it into consideration when there are more puzzles in practice. At present, the result of buying books is a shelve, a bunch of books that I think are useful but I have not read.