Road to Jane read notes 03
How correct feedback to others?
The two sides stressed the common ground, a common vision for the team talk, the other person that is in a safe environment;
Focus on the behavior and consequences, avoiding habits, motivation and nature;
Encourage each other to do the work.
Personal feelings:
Why pair developed it?
Often heard phrase is the power of the team is greater than the individual, in fact, too, in our development process, inevitably requires teamwork, cooperation and sometimes two people, some group of people worked together to complete a project, a few people together to accomplish when in problem solving and design ideas above have more ideas and creativity, which would also make the project our own doing more good, will be more fast problem solving, cooperation to solve several people one problem will become much simpler. Not only that, but also the development of twinning can bring their own more self-confidence, do not want to own one time, once the time the problem will find it difficult to encounter stuck, for a long time will not solve the problem yourself most low self-esteem, over time, confidence will be insufficient. And to complete the knot can develop higher quality of our tasks and projects.
How to other members of our team feedback in the team?
In the development of the team, we inevitably need to meet, but also need to give advice and feedback to other members of the team, but how to give them some feedback is a big problem, I am concerned, I give feedback to others easy to add some personal feelings, sometimes anxious for the project ah also likely to show up in which way is certainly not good, author of the book examples cited in the text, give me a good template, do not give when others suggested adding personal feelings, from the team's starting position wood an objective point out some of the problems, and be sure to give into practice, can not Void, otherwise such a proposal does not provide any practical usefulness and effectiveness, also easily lead to resentment of others, you will ultimately have to give each other some encouragement for the future and some of the Imagination team, which can arouse expectations for the future, but also to do something harder.
Do software requirements analysis, I always feel that the software requirements analysis is a very troublesome thing, it takes a long, long time, remember that video when a team project beginning needs to be published by NABCD to write the transcript later analysis software to start when the team, to do it step by step, knowing that our software users are in those places, those who need to use our software, why people will use our software, there is no advantage and highlights can be compared over other competitors, and now for the software requirements analysis, I felt the need to seriously do, after all, is to give the software to do it with, if they are not clear for the user's needs, how can you go to sell user satisfaction with the software it, Why say their software can be sold, PK someone else's software can do so at the beginning before the software design and development to do, it is important for the user needs analysis.
Finally, the book talked about software design and development, but also nothing too much experience, and now it is no much experience, is in the development process of the software you are experiencing a lot of problems, not just a few people to write Code together less than one, there are a variety of problems, which are experienced and we have to clear a few things. I hope to be able to do some things, a lot of accumulated some experience.