Some people really think there has to be a bug free software ...
- Programmer produces code he believes is bug-free.
- Product is tested. 20 bugs are found.
- Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.
- Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.
- Repeat three times steps 3 and 4.
- Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
- Users find 137 new bugs.
- Original programmer, having cashed his royalty check, is nowhere to be found.
- Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
- Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
- Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
- New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.
- Programmer produces code he believes is bug-free
- Go to … … …
One thing is for certain – skepticism is a trait both positive and necessary for a team! The reason many of us see skepticism in a negative light arises from a skeptic’s difficulty in communicating pleasantly and diplomatically. In order for a team to make the most out of their skeptic, they must first be discovered, then understood and finally communicated with in the proper way.