There’s no replacement for good management. The leader of a team shouldn’t need artificial methods to know whether the group or one of its members is not performing correctly. Having said that, a responsible Test Team Manager should always track and analyze objective and empirical measurements of her team; these metrics will provide very little [...]
Are we there yet? Using Bug Charts to determine the completion of your Development Project
Ever gone on a long car trip with kids? After some time they start growing restless and begin asking every 5 minutes (if your lucky) ARE WE THERE YET? ARE WE THERE YET? ARE WE THERE YET?!?!?! I’ve had similar experiences in Development Projects. Close the release date we’d start getting calls from Product & [...]
Improving the efficiency by keeping track of your waste
All development organizations have a number of recurring events that waste the time of their teams. When reviewing the subject of Defect Lifecycle Management two of the most important undesired incidents are : (1) Rejected Defects – Defects that are reported by the QA and rejected by the product or development teams. (2) Reopened Defects [...]
Using your Kitchen as a Communication Channel
Do you want a simple way to keep your team updated on what’s happening on your project, here’s one: a Kitchen Screen. Most companies have a small kitchen or resting area where people go to make themselves a cup of coffee or grab something quick to eat a couple of times a day. Team members [...]
Process Quality Feedback and Escaping Defects
I was visiting friends and family last week in Costa Rica. Even though there is a growing software industry in there, my non-technical childhood friends only know that I work in “something related to computers” and for them that means I do everything from installing printers to writing the software for the space shuttle program. [...]
Testing Outputs that generate added value to the Organization
Last week we reviewed the operational inputs of the software testing process. This week we should complete the picture by reviewing its outputs. As part of our analysis we identified six channels that provide input to the testing process (Requirements, Scheduling, Designs, Risks, Defects, and Organizational Feedback); output channels are less in number but bigger [...]
- 10 reasons why You are NOT a Professional Tester! — Part 2 December 5, 2011
- Why can’t developers be good testers? May 5, 2010
- Stop being a NON-Technical Tester! December 19, 2011
- 10 reasons why You are NOT a Professional Tester! — Part 1 November 28, 2011
- Manual and automated tests together are challenging May 16, 2011
- Stop being a NON-Technical Tester! December 19, 2011
- 10 reasons why You are NOT a Professional Tester! — Part 2 December 5, 2011
- 10 reasons why You are NOT a Professional Tester! — Part 1 November 28, 2011
- One metric = One Big Mistake November 14, 2011
- Short post – plan your tests, even when you don’t have time to plan them October 21, 2011
- Dmusil: Yes, as a QA professional you should understand a ...
- Ajay Balamurugadas: A must read for every tester :)...
- Bill Schlesinger: I have had these thoughts for years but did not ha...
- Rene Pally: Hi all, I agree with this topic if the tester is n...
- : Yes, this is the point, we need to do our work wit...