???
c
Not for contractual reasons but to see how scared he gets at having to estimate.
d
You need to be very sure that some bought-in system works
before
deploying it. Apologies if this seems obvious but it
wasn??™t to some big companies. Like AT&T wireless.
FIGURE 10.1
Identify outsource project process model A
Start
Identify the reasons
Review all outsourcing
proposals and plans
Assess the threats
Analyze risks
List backsourcing issues
A
Threat checklist
Outsourcing proposals
and plans
Outsourcing proposals
and plans review report
Threat/mitigation list
Risk analysis
Backsourcing issues list
190
Manage Software Testing
4. Analyze and quantify the risks.
5. List backsourcing issues.
6. Create an outsourcing process model showing the quality gates.
7. Draft an outsourcing plan with reference to section 10.2.8.
8. Draft a metrics plan to support the contract(s) and SLA(s). Identify:
a. The questions you need answering (see Chapter 18)
b. The tools to be used to collect and analyze the metrics
9. Draft and review (a) contract(s) and/or SLA(s).
10. Identify (possibly with a model) the degree to which one contract depends on the deliverables of
another. From this determine a critical path and review which contracts are to be co-awarded,
which need coordination, and which can be duplicated either for supplier assessment purposes
or to prevent lock-in.
11. Review the process model, SLA(s), and contract(s) by having the customer staff
act out
various
supplier roles (it shouldn??™t be difficult to get people to pretend to misbehave), and thus identify
the possible areas of failure and the means by which they can be detected and reviewed.
Pages:
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395