In a lot of project there is between all disciplines a kind of “my job is done now it`s all yours” without any communication. We all know that this principle doesn`t work well.
Therefore Quality Gates are introduced. With Quality Gates you define the entry- and exit-criteria per testlevel. With this approach it is very clear for each cluster what to to and they know when their task is completed.

This figure shows a couple of things. The product moved from phase/cluster to phase while the communication is also the other way around. You can just pass the wall if you use the gate. The group on the other side has defined the entry-criteria. So you have to do what they want, and that`s why communication is so important.

These QG`s must be a part of your test approach, or project plan because there are also common entry- and exit-criteria.

Quality Gates

I was just making this figure last week for a presentation, but if you want to use is feel free. If you have any comments at this principle feel free to give them so we can make this figure better.

as shift in mindset of software development is needed from “throw it over the wall” to “bring it through the quality gate”