Found new concept of Software Development Cycle in my company, please read the list below.
(Based on a true story..ha..ha…)
1. Programmer produces code he believes is bug-free.
2. Product is tested. 20 bugs are found by QA Department.
3. Programmer fixes 10 of the bugs and explains to the QA department that the other 10 aren’t really bugs.
4. QA department finds that five of the fixes didn’t work and discovers 15 new bugs.
5. See 3.
6. See 4.
7. See 5.
8. See 8.
9. See 7.
10. Due to “BOS” pressure and an extremely premature product announcement based on an overly optimistic programming schedule, the product is released.
11. Users find 137 new bugs.
12. Original programmer, having cashed his royalty check, is nowhere to be found.
13. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
14. Entire QA department quits.
15. New “BOS” is brought in by board of directors. He hires programmer to redo program from scratch.
16. Programmer produces code he believes is bug-free.
17. Back to no. 1