Testing always happens. Often it happens at the end of a development cycle; even in a small and true agile project, testing happens after other things have been developed.

As projects often run behind the original schedule pressure is placed on the tail of the project – which is usually testing. If we compress testing however, we threaten the ultimate quality of the outcome. Super important but often compressed because rest of delivery late and intent to keep to original timeline:

1. Very hard to control the variables in user devices
2. Specialist test firms do testing very well – not popular
3. Plan in need for rework and bug-fixes

Don’t compress testing if quality or user experience is important! See the next page for the explanation for why MVP and quality is important. This is discussed in the next section.