Prev | Current Page 149 | Next

Peter Farrell-Vinay

"Manage Software Testing"


3
Manny Lehman (private communication).
42
Manage Software Testing
4.3 Test Management Principles
I keep six honest serving men
(They taught me all I knew);
Their names are What and Why and When and How and Where and Who.
Rudyard Kipling
Here are some principles acquired, like most painful experiences, when I was trying to do something else.
??? If you can??™t plan or process model it, what makes you think you can do it?
4
??? Never put into a plan what you can put into a strategy document. Only put the unchanging
essentials into the strategy document. Any part of the plan which doesn??™t somehow depend on
the strategy document is probably not thought through properly. Any part of the strategy document
which isn??™t reflected somehow in the plan is a risk.
??? As soon as you have finished the plan, go through it and see what you can cut out.
??? Limit the things you monitor to the phase you are in, the start of the next phase, and the top
priority alerts.
??? If you lose several of the arguments listed in section 4.6
,
leave. Unless it changes, the organization
won??™t last long anyway.
??? Anyone should be free to raise a bug. If bugs are duplicated the test manager can weed out
duplicates daily at the bug clearing meeting.
??? You must have access to all bugs reported from the field.
??? You are paying test staff primarily for their ability to think. If they cannot or will not do this, then
sack them.


Pages:
137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161