1. Without a mission, you can't define the work that belongs in your group and the work that doesn't belong.

2. A mission should say what you will do and help you explain what you won't do.

3. Beware of missions that promise immediate or continuous response to the organization unless you do have a 24/7/365 organization and the staff to support that service level.

4. It is easier if your manager has a mission, but if your manageer doesn't start with the work you do (and what to do) to generate your mission when your manager develops his/her.

Wrong. While it is true that some QA engineers like to get into the code, and enjoy using automated scripts, there are other folks that prefer a “thinking & building test cases while executing manual tests” type of approach.

Probably within your team you will even have a mixture of skill-sets and different personality types. Similarly you will have folks that started in QA, landed in QA from a different career, are considering a career change, or want to remain in QA for the long term. What is important to remember is this - QA is a valuable professional field that requires intellectual efforts similar to those required to develop a product. Think about it. A QA Engineer is developing the plan that will ensure the success of a company’s product in the marketplace.

Are you really a software tester?  Not just by job title. I mean, deep down, is software testing in your blood.  Do you think like a tester?

Think about this Answers:

Sometimes we tend to forget what we are actually looking for

Q1. Who watches the watchmen?

Q2. Don’t you think the biggest bugs are the hardest to find?

Q3. Isn’t it that the more bugs you find, the more bugs there are?

***