Modern software engineering exercises and discussions Chapter 5 teams and processes

1. What is the relationship between the team model and the team's development model?

The team model mainly depends on the members of the team, including the team leader and team mates. Because of the different personalities, abilities, and IQ and eq of personnel in various roles, especially the aforementioned "attributes" of the team leader ", it often determines a team's "morale" and "perseverance in the face of difficulties", that is, what we often call "soft power ". Such soft power often inspires the great potential of a team and creates unimaginable value for the company.

The development model of the team is closely related to the software development model we are currently familiar with, such as Waterfall, iteration, spiral, and agility. However, it is different from the software development model in the pure sense, this is because the developer factor is also added, that is, the "person" factor. It is a development model that is closer to reality and "grounded.

The relationship between the team model and the team development model can be a metaphor: The two constitute a person, while the former is the brain, and the latter is the body. The body is the sender and executor of the action, while the latter is the controller and dispatcher of the body. Likewise, some teams can develop valuable software to complete difficult tasks and create value. Some teams cannot do this. Because all the software development modes only take development efficiency into account and other issues, and whether the task can be successfully completed in a sense depends entirely on the project performer, that is, the team model. Therefore, the soft power that I just mentioned is an invisible one that contains the internal strength of team members. This invisible strength determines whether a team can make valuable and practical work, give full play to the development model.

 

2. If you lead a new project, how do you choose a "suitable" team model?

 

As a team leader, when selecting a "suitable" team model, we should first focus on the people who need the roles of the team I want to set up, such as po. Secondly, then, based on these different roles, select the persons with their corresponding personalities and abilities to assume this role. Here, I put the role in front of the ability, because I always believe that "personality determines everything, Details determine success or failure", and a person's personality determines his three views, it is important for software practitioners to determine their professional ethics.

Finally, I would like to say that, as a team leader, building a team requires a good corporate culture and powerful soft power. Such a team can always turn into a rope and work together. In this case, we will focus on the technical and other practical aspects. Otherwise, it will easily lead to technical people, cursing the leader in their hearts, and being dissatisfied with their colleagues. In the end, the team's break up into pieces.

 

3. How can different team models affect the evaluation of team performance?

 

Different teams may consider many different factors in performance evaluation. For example, if a team is rigorous, from top to bottom, it will evaluate its performance based on the requirements given by the company and the customer's response, for more "humanized" teams, more human factors may be considered during the evaluation. For example, when the evaluation results are unsatisfactory, it may come up with reflection based on the company's requirements and the customer's response, but it may also come up with the following: "Maybe everyone is too tired recently, or the person responsible for the unsatisfactory module has some things in the house recently ".

 

4. What is the difference between team spirit and collectivism?

 

In my opinion, the Team Spirit emphasizes a strong momentum and a soft power. Sometimes different teams have different team spirit. For example, if some teams are efficiency-oriented, their team spirit emphasizes efficiency and completes work on time. Such teams are sometimes dull, lack of vigor; and some teams are cooperative, so their team spirit emphasizes that everyone's heart is gathered together and there are things for everyone, like a big family, a high degree of human nature.

While collectivism sometimes emphasizes consistency. As long as this collective completes some work, it ignores the individual's role and focuses on the general purpose. It often regards a collective as a person, the requirements for a person are magnified to the requirements for everyone, and sometimes there is a "one-size-fits-all" feeling.

 

5. Read the book dreaming in code to analyze the forms and processes of the Chandler team. What are their advantages and disadvantages?

 

 

6. Some people say that modern software engineering is divided into four stages: quarreling with PM and design, and having a test quarrel with users. How do you think we should avoid quarreling?

 

Quarrel is due to misunderstanding, and "99% misunderstanding is due to poor communication". To avoid quarrel, we must first communicate and communicate with knowledgeable people, let both parties understand the difficulties of each other. Second, we need to achieve each stage of software development.

Prior to the start, we decided on the other party's final plan, the solution, and the satisfaction of each other. After a unified statement, we began to work on it. We wanted to spend more time on projects rather than disputes.

Modern software engineering exercises and discussions Chapter 5 teams and processes