Software Project Management and Saving big soldier Ryan

Recently, I have reviewed "Saving big soldier Ryan" again. I have some ideas to share with you.

1. First, clarify the project objectives and user needs. In most cases, it is the requirement of the leaders, that is, to save the hope of Ryan. Of course, the background of the project must be understood, in this way, I can deeply understand the project objectives. In the project team, I was the first to contact the customer's needs. Generally, I converted the requirements into functions that can be implemented by the Software. At this stage, the commonly used tools are UML. Of course, the user's Requirement documents are all completed by me and confirmed with the customer.

2. Determine appropriate resources. Some of these resources are internal, some are external, and the external resources are often uncertain, for example, the German translation "oupham", which is newly added to the film team, is unpredictable;

 

3. Make a plan and allocate appropriate resources. Simply put, let everyone find their position in the project and make full use of their expertise, for example, a sergeant with a adviser is like a technical manager in a project who can discuss decision-making issues and has technical expertise. Another example is that Jackson is a good employee who can always faithfully execute projects and perform their duties. At this stage, I use projects most, and I am used to weekly meetings, so that I can be aware of the implementation of the project.

4. process management, handling various contradictions and conflicts. In this process, you cannot take into account your personal gains and losses to serve the public. For example, if you do not understand the project objectives, when someone says about your gains and losses, you can answer the question correctly. For example, to save the team set up by Ryan, it means that Captain Miller has lost his company. His answer is "It's not my connection, it's the whole army, we must obey ", there are many such examples, and there will be different stakeholders. Different people are suitable for different methods;

5. Change management is inevitable. For example, there is a clip in the film that destroys the machine gun position. At that time, most of the Members opposed this change. Sometimes, instead of persuading them, it is better to set an example by yourself. This requires you to use software development tools. For example, I often browse the project code and perform coding in person when necessary.

6. In the end, performance appraisal is also necessary. teamleader must have the penalty power. Of course, I may not necessarily run these powers. At least it is a deterrent to some people. We all know that it is a nuclear deterrent, I personally think that deterrence is more effective than actual punishment.

 

With these conditions, it is only a matter of time to complete the task. Even if there is only one shot left, the project must be completed.