看到有一篇介绍关于QA Management 需要的技能，post到这里作为参考：
--------------------------------

QA Manager Required Skills

• What a QA manager does

1. Planning, prioritization of all the test-related tasks (use proven project management tools such as the V-Cycle or Scrum methodology)
2. Writing the test strategies
3. Reviewing the test plans
4. Taking the responsibility of certain designs if people have not the required competencies
5. Code reviewing
6. Spreading expertise and good usage of tools such as bug-tracking database or versioning systems
7. Delegating...
8. Having people judgment skills to hire the right people
9. Writing performance review

• What makes a good QA Manager

Being a good QA engineer
Of course, a good QA Manager is first of all a good QA engineer. It requires additional skill, though.

Effective communication
A QA Manager must be an extremely good communicator. This includes:

1. Report global status and risk analysis to top management
2. Capability to communicate with technical and non-technical people
3. Having the diplomacy to say "no" when global quality is not acceptable for release
4. Part of the communication is also the not so well appreciated "meetings". Meetings are useful to a good organization, though.

For large teams, privilege:

1. Formal meetings
2. Scheduled and iterated on a regular basis
3. Production of agendas (pre-meeting) and minutes (post-meeting)

For small teams, privilege:

1. Stand-up meetings
2. Not necessarily planned
3. Agendas an minutes not necessarily needed

Having and spreading the "customer-focus" vision

To have the QA engineers efficient in their work, they must have the desire to see customers happy.

Developing people

1. Developing people in a QA team as in any team is essential. The main goal is to improve the learning curve and this can be achieved by:
2. Spreading best practises you've learn along your whole career as QA engineer/manager
3. Organizing trainings (external as well as internal)
4. Working in group to share competencies
5. Leaving some time to people to let them learn by themselves

Bringing out creativity in others

1. This can be achieved by:
2. Organizing brainstorm sessions on a regular basis
3. Discussing a lot with QA engineers to lead them to have the "idea" instead of exposing directly the idea (if you've got it before them). A good QA manager teaches the "way of thinking" before anything else
4. Explaining any decision you take so that the team get the intellectual process that led to that decision
5. Working in group

Motivating people

1. Motivating people is also necessary. To do that:
2. Be motivated yourself
3. Share your motivation to the others
4. Explain why QA is an interesting job:
5. Too often, people are reluctant to do QA because:
6. "QA = finding problems = people (dev.) don't like me"
7. The good way of seeing the job is:
8. "QA = avoid future problems = people (dev./support/customers) like me"
9. The result of QA activities is immediately seen by the end-user which is quite valorising
10. Seeing a "manual operation" becoming a completely automated job is demonstrating how talented people can use machines to improve life
11. Thoroughly testing a feature A is often more complex than developing the feature A. It's then a challenging (so enhancive) task.

Team building
A "dream" team is a team where all people are technically very good in their job but also like to work together and appreciate each others. To improve the chances to have this happening, a QA manager shouldn't hesitate to:

1. Organize events (these do not necessarily require expensive activities!)
2. Have some chats together on the working hours about non-technical subjects when the whole team is present
3. Have QA people cooperating more with other teams (especially with Development team)
4. Have a beer together sometime ;)

Enabling changes
Changing for changing is a bad concept. Conversely, when something does not work, change is mandatory. The process of changing must go through 3 steps:

1. Making an audit to see what's wrong in the process (i.e. difficult to maintain very similar test scripts)
2. Determine with the team what has to be changed (i.e. setup data-driven testing)
3. Implement the change

Decision making

1. In QA manager there is "manager", which means that this includes making decisions.
2. Not being overwhelmed by stress
3. Not hesitating to recognize a mistake soon - it is much better than trying to workaround for years the issue
4. Taking innovative (or risky) initiatives
5. Not hesitating to change the processes at risk to destabilize some people if you think it is necessary

---------------------
FW: http://www.xqual.com/documentation/tutorial_qa_manager_skills.html