Negotiate a per-project contract. This need only be signed much later when requirements have
been identified.
15. Review contract(s) to find weak points particularly milestone and quality gate definitions.
16. Establish overall management group and bridgehead teams. There will be usually a management
group drawn from both organizations charged with relating the two halves of the project. These
will be concerned with the strategic direction. The bridgehead teams will be concerned with dayto-
day liaison between the groups and will report to the management group.
17. Handover existing documentation (specifications, code, manuals training materials, and tests)
using the common document management system. Off-shore staff should mine all the project
documentation and generate:
a. Indices of all available documents plus ???read-mes??? describing the contents of each one. (This
will help them get some idea of the extent of the project and will add to the customer??™s trust
that the supplier staff comprehend.)
b. Architecture and network topology diagrams.
c. Feature descriptions identifying for each feature:
i. Introduction and background
ii. References to any plans
iii. Glossary of feature-related terms
iv. The requirements and design specifications
FIGURE 10.5
Find the supplier process model C
B
Modify the
metrics plan Metrics plan
Overall relationship
contract
Per-project contract
Terms of reference
Updated
outsourcing plan
Documentation
Glossary
Update
outsourcing plan
Handover
documentation
Write a common
glossary
Stop
Risk analysis
Backsourcing
issues list
Negotiate contracts
Review and modify
contracts
Establish overall
management group and
bridgehead teams
194
Manage Software Testing
v.
Pages:
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399