RISK MANAGEMENT SOFTWARE DEPLOYMENT: YOUR GUIDEBOOK TO SUCCESS 28
Testing deliverables as they're delivered means that user input should
be solicited throughout the deployment — not just at the end of the
implementation or at a critical juncture. By doing so, the client and
RMIS provider are more likely to uncover issues that will be most
effectively addressed before the next deliverable is delivered.
SECOND: TEST EACH DELIVERABLE AS IT IS DELIVERED
The actual users should be involved early in the process to make sure
the RMIS provider understands their business requirements and that
test cases and test scripts align with those requirements (more on test
scripts in a moment). In fact, we encourage users to help define the
actual test steps for the business testing, and that happens at the very
beginning of the project.
Clients often ask us who should be involved in testing. We recommend
having end users from various parts of the organization.
When we start an implementation, we begin talking about testing as early
as the requirements gathering (or discovery) stage and we make sure it's
included in the project plan.
FIRST: ENGAGE USERS FROM THE BEGINNING
