OPPapers.com

Contract Creation And Management

Contract Creation and Management
Introduction
This week’s simulation looks at the relationship between Span Systems, a California-based e-banking software developer and their client Citizen-Schwarz AG. Citizen-Schwarz AG is a Stuttgart, Germany-based company looking to break into the American banking market. This document will be written to Span Systems Director of Projects, Kevin Grant. Citizen-Schwarz AG is dissatisfied with Span Systems and wants to break the contract. This is my outlook on how to retain the contract and improve Span Systems.
Changes to Original Contract Requirements
During the initial 8 months of the contract, Citizen-Schwarz AG has added to and made changes to the original contract. This has created problems with both meeting promised deadlines and decreased the quality in deliverables. Kevin, I suggest we make the following changes to the contract:
1) Create a Change Control Board. The board will consist of a project manager and a lead software engineer from Span Systems and Citizen-Schwarz AG. The Board will decide what changes to accept or reject. Both Span Systems and Citizen-Schwarz AG will abide by the decisions of the Board (Contract Creation and Management).
2) We need to increase our manpower for this project to ensure our deliverables are on time and of highest quality. I recommend we add at least 10 additional programmers to the project.
3) Finally, I would charge Citizen-Schwarz AG for any additional changes to function points after the contract is signed. I suggest the following breakdown:
a. Features added 3 months after signing the contract would be $1,100 per function.
b. Features added 6 months after signing the contract would be $1,250 per function.
c. Features added 9 months after signing the contract would be $1,500 per function.
d. Features added 12 months after signing the contract would be $1,750 per function.
The Change Control Board would be responsible for determining all changes (Contract Creation and...