Virtually every technology project requires some new system or process to be tested before it is placed into production. Experienced project and operations managers understand that no amount of planning, organizing, training or practicing can substitute for an actual test drive in identifying errors and mistaken assumptions about how something will work in the real world. Business-oriented testing requires design of test cases with expected outcomes, based on real-life expectations of new systems or processes. This approach, required for large, complex projects and beneficial for many others, frequently makes the difference between highly successful projects and mediocre projects with middling outcomes.

Although much has been written about the best way to test new systems or operational processes, with planning and forethought business-oriented testing can be executed fairly easily with the following 10 steps: