About team building and personal growth _ test Management

About team building and personal growth

A summary of ideas about team building and personal growth, from the views of colleagues in the team meal, feels pretty representative, so sharing it doesn't involve any company privacy.

1. When it feels like the team is not in the right place, or if something is wrong, or if there is a disagreement about one thing, everyone has a responsibility to express it at the first time, the goal is to make the team better;

2. To output good documents and interfaces in time to output documents, output good documents, can greatly improve the efficiency of the team

A team is like a team, you want others to give you the passing is comfortable, you pass the ball to others is also better to get in place, more from the user (the other) perspective to consider the problem: architecture/process/interface is not good understanding;

3. The team should have good communication and knowledge mechanism, the information can reach everyone in time

Everyone should know what the team blueprint is, what the immediate goals are, what the team is doing now, and what the current difficulties are;

4. Colleagues should be more exchanges, promote each other, collision sparks, which is also a team attractive symbol of one;

5. Another sign of passion and attraction to work is whether the things that are done are challenging;

6. The team should pay attention to everyone's growth, of course, technical improvement and growth, more personal things;

7. Regardless of team or individual, more to sum up the reflection, multiple recovery disk;

8. Routes and milestones are important, busy for some time, reached a milestone, should be a little reward;

9. The functions that are seriously done, are rarely used now, or have little user feedback, which makes people feel no sense of accomplishment.

Existing products, should increase the collection of user feedback, which for the follow-up improvement and work is very valuable reference;

10. The ability to look very strong in the interview, non-productive quantity and efficiency, not necessarily comparable to the appearance of the normal personality and characteristics of the people is very important;

11. Everyone should output more output ideas, opinions, opinions, summaries, articles;

12. To maintain the integrity of the module concept is not appropriate to the requirements of the say in the module, to be no;

13. Do something for yourself. For programmers, code should be written decently;

14. Walk feature owner's way, the developer's scope is too large (responsible for requirements collection, collation, development, project progress, test arrangements, release, all horizontal and vertical communication, resource acquisition, etc.),

May cause people to not focus on development, and shrinking scope, developers are only responsible for specific development actions, may be a lack of understanding of the entire product needs to weigh;