Chapter 2
1. Compare performance evaluation methods of different teams and propose performance evaluation plans of their teams
Although different team models have different advantages and disadvantages, we prefer to select the first team for the teams provided by Mr. Yan Xin.
First of all, everyone is a level-1 worker to a large extent, which makes our team maintain a close and friendly atmosphere. The tasks are constantly refined so that everyone can perform their respective duties and work together for a big goal, no one in a team wants to delay the progress of the entire team for their own reasons, which also makes every team member feel a sense of urgency. This helps every member of the team get real training and learn to take responsibility.
2. Will there be "Bad currency expelling good currency" in the team?
In the process of a team's project, everything may happen. Of course, we do not want this situation to disturb the normal operation of the team, therefore, we need to rely on the strength of every member of the team to control and reverse his appearance.
3. Read drive and responsibility [ll1] to discuss how the team can make everyone clear about drive and responsibility.
It is necessary to establish a sense of honor for each person in the team and know that they are integrated with this team, so as to truly put the interests of a team first.
4. Get out of the "self" and "present"
In this course, we can first feel the knowledge of Software Engineering more vividly. In addition, unlike other courses, This is a course that closely integrates theory and practice, so it is helpful for us. We have the opportunity to personally explore software engineering and start from a small team to feel the experience of a team.
5. Course scalping software and ticket scalping Software
It is of course a good thing for us to develop it with hands-on skills. However, if your own development harms the interests of others, it is not good. A good software is designed to help you, it cannot be at the cost of harming others.
6. How do teams make decisions?
Software development and the survival of Software Teams are faced with many problems that require many wise and decisive decisions. How can a team make decisions? The following methods are available:
A) Dictatorship: leaders have the right to decide.
Advantage: there are not many disputes, so it is not easy to disagree with each other and there is a fast progress.
Disadvantages: if there is a problem in the general direction of the leader, for example, if the foundation of a building is not well laid, the road will be harder to go in the future.
B) Dictatorship + consultant: Leaders Discuss with some external consultants before making decisions
Advantage: with the adviser, it will not be too arbitrary or arrogant, but can also absorb suggestions from various parties.
Disadvantage: You can only stand in the perspective of expert consultants and leaders, while ignoring more people in the team.
C) democratic voting: This leads to winners and losers.
Advantage: more fairness, justice, and democracy are enough, and comments from all of you are included.
Disadvantage: more time consumption
D) after the unanimous consent of the whole, I decided: Are you happy?
Advantage: everyone is very happy.
Disadvantage: The progress is slower.
7. Professional Ethics comments
Select some recent events in the IT industry (for example, an employee deletes all the data on the company's servers due to personal complaints) and compare them with the professional ethics of software engineers, evaluate the professional ethics of software engineers.
From the perspective of professional ethics, there is no professional ethics at all. It is a lack of respect from practitioners in this industry, and it also blurs their own character. Appropriate legal provisions should be provided to sanction and punish them.
Modern software engineering practice and discussion Chapter 1 human, performance and professional ethics