14 things the software project manager should be most concerned about

The primary responsibility of the software project manager is to ensure the success of the project. How can we ensure project success? Some things and keywords are very important for software project managers.

Different industries, enterprises, organizations, projects, and PM may have different concerns. The following lists some things or aspects that we think are the most important.

1. People-human

The first is human and.

Similar to any engineering project in other industries, software projects cannot be successful without harmonious interpersonal relationships.

1.1 customers and users-build a good relationship between customers and users

Meeting the needs of customers and users is the first priority. If the customer is not satisfied and unhappy, is the project still possible to succeed?

Therefore, it is particularly important to establish a good relationship between customers and users from beginning to end.

Many customers are not it/software experts. They mistakenly think that software development is similar to building a house or creating a car. How can we better engage the customer and get the understanding and close cooperation between the customer and the user? This is a problem.

1.2 The team-Team

No PM does not want to have a good team.

1.3 collaborate with communication-cooperation and communication

To complete a project, you often need to rely on external forces to communicate closely and effectively with stakeholders (such as other departments and teams, suppliers, and partners.

1.4 culture, goals and values-culture, goals, and values

Enterprise culture and team culture are very important.

Taiji software engineering holds that CMT: culture determines management, and management determines technology.

If all stakeholders share a common goal and value, the project is easy to succeed.

1.5 politics and economics-Political Economics

As managers of any company, every PM should understand political and economics. If PM lacks political and economic minds, it is impossible for him to sit still in this position.

2. Reuse first-reuse (or reuse) is preferred!

Unfortunately, over the past 10 years, many people have talked about process improvement, process management, and quality management, but few have talked about systematic reuse ).

Reuse is not a silver bullet, but a gold bullet!

How can we minimize the necessary work?

3. process and methodology-select the most appropriate project process/process and methodology

Process management and improvement have been a hot topic for global management and engineering over the past 20 years, and the software process is no exception.

Most of the problems and troubles encountered by a software enterprise or project team are directly or indirectly related to the process issue. Therefore, we must first clarify the process. Is it important or light?

What is the best process for software development? What is the best method for software development and management?

What process and methodology should my project team adopt?

4. Models and documentation-models and documents

How can we communicate more effectively?

Oral Communication is not reliable. It is best to form a written document, in black and white, with evidence to be found.

Graphical Modeling is not only an instinct of humans, but also an important means of communication.

5. Risks-risks

Risk management is the first management of software project management.

PM is aware of risks and maintains a risk list every month. It is a best practice for risk management.

6. Requirements (functional and non-functional) and scope-requirement (function and non-function) and scope

The demand (to do what) is located at the upstream of the software development causal chain. The demand definition is unstable, incomplete, and the quality is not high, it often leads to a series of errors in downstream work, such as estimation and planning, design, programming, testing, and so on, resulting in rework, overspending, and overrunning of software projects.

Therefore, the project has already been half-done by PM, who pays close attention to the demand.

7. Plan, review and adapt-plan, review and adjustment

Planning and writing many management documents and reports are the primary responsibilities of PM?

Well planning is indeed a very important task for PM. Everyone wants to make everything ready for planning, control, and control. Such a project is naturally easy to do.

But the truth is that, in complex software development projects, there is a saying that what remains the same forever, and the law of the universe tells us that motion and change are always the same, static and unchanged are relative.

Traditional methods and agile methods are significantly different in terms of planning. Traditional methods emphasize a perfect plan in advance, while Agile Methods emphasize timely feedback, review, and adjustment. By organically combining the two, we can be invincible. (Taiji)

8. Time (timing), schedule and progress-time, schedule, and progress

Tianshi has always been a hot topic and a core issue.

What customers and leaders are most concerned about is: when can this system be truly delivered?

Currently, the best software development method for ensuring progress and on-time delivery is iteration ).

9. Testing and verifying the quality-test and quality

Once there is a problem with software quality, it will cause a lot of trouble for the project.

10. Measurements and metrics-metrics

How can we reduce head shot decisions?

Quantify and use scientific data.

The more metrics, the better.

11. architecture and design-system/software architecture and design

Taiji software engineering holds that architecture design is the main content and contradiction of software design. The quality of architecture determines the quality of software systems.

PM should work closely with architects in the team to eliminate technical risks of the software architecture as soon as possible.

12. Reduce Cost-reduce costs

The project manager must settle the account.

Time cost is a major hidden cost.

13. Optimize management-optimization management

What is management?

Management Actions: planning, estimating, controlling & monitoring, leading, reviewing, adapting, coaching and serving-planning, estimation, monitoring, leadership, review, adjustment, coaching and service...

Different values and different philosophies lead to different management concepts and methods.

14. Keep learning, accumulating knowledge and experience-persistence in learning and accumulation of knowledge and experience

An experienced PM will pay close attention to the continuous learning, updating and accumulation of personal management knowledge and experience.

Values, principles, patterns and practices (VP3)-values, principles, models, and practices

We recommend that you refer to the VP3 structure to organize your knowledge and experience.