No Questions, no Issues. Period!
  • Easy
  • 40 min

Once we deliver the software to users, we’re not there to answer questions or solve problems when they occur. It should simply work without problems. When introducing the concept of Zero Defects, one trick used is the challenge that at the final test there should be “no questions, no issues”. If the testers would have even just one question to ask or find even just one issue, the test is to be aborted as failed. My experience is that in no time the quality of the deliveries improves dramatically.

We’ll see two cases where I challenged the developers and testers with the “no question, no issue” requirement. The first case was a Scrum team that even succeeded in the next sprint. In the other case, a developer/tester team had been doing ‘system test’ after ‘system test’ for months, every time uncovering new problems. It took a few iterations for the team to find out my requirement was dead serious, but then quality increased dramatically and they finally delivered successfully.

Comments ({{Comments.length}} )
  • {{comment.AuthorFullName}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to

Chat with us, we are online!