4) to be used by the supplier using a process
model. In particular note where the processes use the common systems mentioned in point 11 below.
7. Update backsourcing issues list.
8. Identify critical issues and processes which must be monitored to warn of relationship failure.
9. Identify and agree a handover process with the supplier.
10. Agree a change management system with the supplier.
11. Agree a communications system with the supplier. This will include the primary contacts, the meetings,
the reports and their formats, and the visibility of the supplier development environment by the
customer. It will require that you and the supplier use or have access to a set of common systems:
a. Email and videoconferencing
b. Document management
c. Bug management
d. Code management
e. Test management
f. Time sheet management
Agree email response types and times, and note this in the SLA. This approach uses a common
set of unit-testing tools. By having these common systems the supplier-customer relationship can
be greatly enhanced from the mutual trust each has or alternatively the failure of either party to
use the common systems will act as an early warning.
12. Modify the metrics plan to account for the contract and SLA requirements (Figure 10.5).
13. Negotiate an overall relationship contract. This will cover the major issues including the principles
on which testing will occur.
FIGURE 10.4
Find the supplier process model B
A
Identify and agree the
development process
Update backsourcing
issues list
Outsourcing
process model
Backsourcing
issues list
Change management
system
Communications
system de?¬?nition
Identify critical
issues and processes
Identify and agree a
handover process
Agree a change
management system
Agree a communications
system
B
Outsourcing
193
14.
Pages:
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398