10 things that should make any self-respecting Test Manager
Imagine that you buy
a TV. The seller tells the story of the two models you like. In the first model
he describes as an image, a heap of potential to save the channels and
convenient remote control. According to the second TV, he teaches you, for any
antenna must pull, if you suddenly lost connection, and what to do with noise.
What TV will you choose? Of course, you want to just sit on the couch to change
channels and you do not wish to burn all the time something to correct!
Management of something like the purchase of the TV. You either build an
efficient process by which you can only admire the picture quality - either you
are always busy with small operational objectives, which basically boil down to
solving problems. How to buy a quality TV in test management? 10 basic rules of
success you’ll find in this article.
1. Form a team of
competent and invest in its development. If your team is not qualified, you
will have all the time to solve problems and understand all the issues. If you
build a team of professionals and show their potential, then you will only be
denoted by strategic objectives (which, given the growth of the team, also will
be able to continuously grow!).
2. Learn to delegate. Micromanagement
inherent in novice managers, many a habit - in the end, you do not give to
develop their team and themselves all the time occupied by minutiae. Therefore,
try to regularly increase the difficulty and complexity of tasks: so you will
motivate and develop their team. And in any case does not fall into the trap of
"no it will not do better than me." Look closely at their employees!
3. Implement effective
test design. If you have a flexible process with the research or testing of a
session, it will be enough high-card functionality, for example, printed on a
large sheet of drawing paper and hung on the wall. In a more formal approach
you will need the test cases, the use of which claims to the test design is
even higher: the optimization tests, reduction of labor costs, transparent
reporting … Invest in a thoughtful and competent test design and performance of
your team will come to a new level!
4. Will be tested. You can use a
formal test plans, self-developed web-based system, MS Project or ekselevskie
plates. But you are in any case would require the collection of statistics on
labor costs, a minimal test-design and a deep understanding of the planning
methodology. Due to the presence of a good plan you will be able to evaluate
progress, and therefore - the necessary measures, if something goes according
to plan.
5. Implement a regular
collection of quality metrics for your product. You can always say
‘it seems, everything works, but for the predictability and the possibility of
making the right decision to release the product much better would be to use
more specific metrics. The number and complexity metrics will depend on the
project, but the automatic collection is probably a universal requirement -
otherwise it’s too fast you get bored, and well, it would seem, the habit will
be forfeited at the root.
6. Define the strategic
goals of Software testing services. "If the stars are lit - hence, it is someone needs."
Identify the mission of its parent star - why you need to test on your project?
Put on the basis of this specific policy goal. This will help not to stray off
course and make informed decisions.
7. Regularly assess the
effectiveness of testing. As we would not want a perfect process is
virtually unattainable, but we can investigate the impact of testing on a
regular basis to improve current performance. Implement a regular assessment of
the effectiveness of using metrics related to your goals of testing. Thus,
you’ll find the "weak zone" that must "pull" - for example,
the quality of the institution of defects, the time to test a single assembly
or the percentage of missed errors. In addition to detecting problems, you’ll
also see the progress and positive - which certainly is good news
8. Keep your employees
informed. Provide them a maximum of information about project status, strategic
objectives, challenges and problems identified. Firstly, it would raise the
team spirit, and secondly, employees can more efficiently carry out their tasks
on the basis of such information. Implement a practice of regular notification of
all news team: do not underestimate the benefit from this and keep people in
ignorance. Create a newspaper, intranet portal, organize stendap or Sitdown
protest. Whichever method of informing you choose, the cost of its
implementation must be paid back.
9. Naladte communication
with developers. Provide a common understanding of your overall objectives. Ask the
developers what they need and what is missing: for example, it is possible that
they have a claim to the defects of which you have not thought about, but which
substantially facilitate their lives. Do not hesitate to return to claim what
is missing you: regular assemblies, information on the changes… Communicate
more often and more constructive: from this will benefit all the participants
individually, and the project as a whole.
10. Implement risk
control quality. Hazards of quality will make your test-design more efficient and more
predictable product quality. You can use the risk of quality as the main
instrument test analysis, or as an additional method for generating tests. But
for any of the approaches you should bring it to the end - "partial"
control of risks can not be.
The above-described
10 tips - this is a minimal basis, necessary for you to comfortably sit on the
couch with a remote control and enjoy high quality pictures. Do not spare the
time to introduce these innovations and do not expect that a theory without
practice is to bear fruit.
Comments
Post a Comment