“No Time to Test” – an approach to starting the testing journey with people who think module testing is all you have to do.
You are called in by a development manager who is suffering because of crashes in the system causing outages at critical times and significant revenue losses. They know they have to do something about testing but doesn’t know how to get started or obtain buy in. The situation is that the system is huge and complex. To properly scope out a full functional and regression test plan might take years. At the same time the developers are not interested, providing the blame cannot be pinned on them.
The point of this session is to discuss how to present a strategy that will allow you to make a realistic start without promising the undeliverable.