In developers we Trust. The rest we Test.

Tester Acceptance Criteria Checker Requirements A tester knows that even if the product meets the requirement to the T , the product could totally suck. So, they do not rely too much on the requirement to measure product quality. A checker is heavily reliant on showing the acceptance criteria is met. They won’t go into testing without a document. Test Cases A tester writes product based test cases. They  ensure test case longevity with data set up and tear down info for fast execution A checker checks the acceptance criteria. They do not know they need to plan for the future, they focus on the bare minimum. BUGS A tester works to find issues that wont show on the surface A checker works to find issues inside and within the acceptance criteria. Purpose A tester explores the product and understands what it does and how is does it. A checker checks the surface ...

I just watched a movie called Shark Exorcist (It is a real movie, someone wrote a story and spent money on making it - http://www.imdb.com/title/tt3120314/ ). I was thinking about what could have made the movie better since a team of people worked on it, they must have had hopes for it. I mean when we make dinner, we want it to be really tasty! When we put on makeup, we want to look pretty! So, what could have been done to make this movie better? Answer : Obviously, Not make the movie at all.  I got to thinking - if the makers used the waterfall methodology to make this movie they may not have had a chance to look at the whole product till the very end, so they may not have known about the lameness of the movie. If they had used SCRUM methodology in the movie making, they might have realized they were just wasting money and might have scraped the project in its initial stages and my 5 minutes would have been used on another terrible shark movie.  (watched in Fast For...