Showing posts with label Agile Testing. Show all posts
Showing posts with label Agile Testing. Show all posts

Friday, July 6, 2012

The 3 Rules of Snakes in Testing

Jim from Netscape was renowned for his ability to voice his beliefs and summarize situations in manner at once ‘down home’ and exactly to the point. Barksdale’s “rules of snakes” where snakes allude to business issues and problems can be also be applied to testing profession.

Below is my version of Jim’s snake-ism rules:

Rule 1: Think of bugs as snakes, if you see a snake, don’t call committees, don’t call your buddies, don’t form a team, don’t get a meeting together, just kill the snake.

Learning: Report the bugs as soon as you find them and highest priority should be tracking them to closure.

Rule 2: If you kill a snake, or get a bug fixed, tell other testers and developers.

Learning: That way they too can keep a lookout for them in that area.

Rule 3: Don’t go back and play with dead snakes or bugs that have clear resolution.

Learning: Once the resolution and the impact is clear, it is advised not to keep spending more time on it.

Friday, December 16, 2011

Agile Test Estimations using Poker Planning (QAI STC 2011 - Published)


This artifact offers a template and guidelines which can be used by agile teams to commit to stories for a sprint using the proven top-down "Poker Planning" technique (for both Developers and Testing) and the capacity in hand.


The poker player learns that sometimes both science and common sense are wrong; that the bumblebee can fly; that, perhaps, one should never trust an expert; that there are more things in heaven and earth than are dreamt of by those with an academic bent. (David Mamet)