Define Customer and Project Responsibilities
The first step is to explicitly identify which parts of product acceptance process will be the
responsibility of the customer and which will be the responsibility of the project team. You should also
explicitly identify the individual or group who will make the final acceptance decision. Responsibilities
can include such things as:
-
Delivery/pick-up of software and documentation
-
Installation of hardware/software test platforms
-
Provision of test data
-
Provision of resources to conduct the acceptance tests
-
Timely turn-around of acceptance test results
|
Document the Product Acceptance Criteria
The product acceptance criteria are defined and agreed during the Task: Initiate Project during
the Inception Phase and should be captured in the Product Acceptance Plan at that time. During the
Elaboration Phase, the criteria can be expended in greater detail when specific tests reviews can be
identified.
These criteria should be developed jointly by the customer organization and the project team, and may
include the following:
-
Delivery of all work products identified as deliverable to the customer
-
List of required participants for acceptance testing
-
Required test location(s)
-
Successful completion of the work product evaluations identified in the Product Acceptance Plan
-
Successful completion of customer training
-
Successful completion of on-site installation
-
Measures that will identify to what extent original project specifications have been met
-
Measures that will identify to what extent the objectives of the business case have been met
|
Identify Artifacts and Evaluation Methods
Next, identify which project work products are to be delivered to the customer for acceptance. For each of
these you need to identify the evaluation method(s) that will be used to ensure the work product meets the
specified acceptance criteria. Later in the project, detailed review checklists and test cases will be
developed to provide step-by-step instructions on how these evaluations will be carried out.
|
Identify Required Resources
Once the numbers and types of work product evaluations have been identified, identify in the plan all the
necessary resources that will be required to conduct the product acceptance task. You should include in
your list of resources:
-
Personnel
-
Computer hardware
-
Software
-
Data
-
Documentation
-
Any specialized equipment
|
Define Product Acceptance Schedule
Another common problem with the product acceptance process is where the customer places insufficient
priority on the acceptance task, with the result that the process drags out over a long period of time.
It is a good idea to include in you Product Acceptance Plan a schedule detailing when the various
acceptance evaluation tasks are to occur. This schedule will become "rolled up" into the master
project schedule in the Software Development Plan.
|
Define Problem Resolution Process
This final step is also very important. Should problems arise during the acceptance evaluations, it is a
very good idea to have an agreed process to follow. Typically this would simply follow the projects problem
resolution process as defined in the Problem Resolution Plan. However is is also helpful to cover off
issues such how to reach agreement that a problem is real, the provision of funding for additional work by
the project team, or contractual penalties. By agreeing all these things up front with the customer, you
will greatly smooth out the end of your project.
|
|