Project Manager: whether the company's strategic objectives or project objectives are achieved. the specific goal is generally measured by profit. The contract price of a project is mainly determined by the Sales Department. The project manager must accurately calculate the cost to cooperate with the quotation, and control the cost in the project process. Sometimes, profit is not a priority. Other possible goals are to win customers, start brands, train teams, etc. If you are the first target to start a brand, you must strictly control the quality, cost and profit are not considered. The company can list a number of goals in a prioritized manner. If the project manager can achieve the first few goals, it will be successful. If it is all done, the Project Manager will be amazing.
Demand ANALYST: after the project is implemented, the less the customer needs to change, the better the performance of the demand analyst. The work of the demand analyst has a great impact on the project's success or failure. It has high requirements on people, such as communication skills, business familiarity, and judgment capabilities (potential needs ), understanding of the customer's organization (who has the say)/Personnel (personality, etc.) and the system operating environment.
System Architect: the architecture of the entire project remains unchanged. If there is a change, the architect's work will fail. The system architecture is based on the results of the demand analysis, so sometimes the architecture changes are attributed to the demand analyst. In fact, the current software architecture has a lot of information, basically knowledge, and there are not many opportunities for innovation, such as David H. hansson is dissatisfied with the hassle of web development. There are very few examples of creating rails on Ruby. Most of us choose mature frameworks and technologies. Architects need extensive knowledge and long-term experience. It also tracks the latest developments in software technologies.
System designer: after the project is implemented, the smaller the workload for maintenance and development (for new requirements), the better the performance of the designer. The designer's work is the most innovative part of the project, exquisite model,AlgorithmDevelopment and the company's core technologies all come from here. The work of different designers may come from the ground up. Of course, they can run without cleverly designed software systems, however, subsequent maintenance and development will surely become a cost black hole.
Software developers: the number of software bugs, the time for fixing bugs, and the severity of bugs, the company can have a formula to quantify these indicators. The work of the software development engineer is the basic guarantee of the project quality, and the software system will eventually become finished here. Many times, software developers also work with design work, so their importance is even greater. Good developers are mostly good designers, becauseCodeIt is also designed.
Test Engineer: number and severity of bugs after software implementation. Both developers and testers use the bug indicator, but these bugs should be calculated independently. Here, the bug is generalized. For example, stress testing is not enough, and it is also a serious bug.
Finally, the architecture, design, development, and testing are repeated. The situation is complicated here. For example, the low quality of Code leads to a sharp increase in the workload of testers, here we need the wisdom of the Project Manager. The specific analysis of the specific situation shows that the requirements for the project manager are comprehensive, and the project manager needs to be responsible for the team's morale, software development is the most important factor for human beings.
The project manager is responsible for recording all project data in real and accurate ways. This is the basis of performance appraisal and must be fair, fair, and open! (