Common use of Project Management Process Clause in Contracts

Project Management Process. IBM 's Project Management process is based upon the premise that the IBM Account Manager will have overall responsibility and accountability to meet all agreed upon quality, cost, schedule and technical objectives of the project. In addition, each Party will assign an individual to each project to act as its respective representative with responsibility for specific operational roles as described below and further delineated in the Project Plan ("Project Manager"). Based upon the scope of the work and the Deliverables to be provided under a project, a Project Manager may be assigned to oversee multiple Projects. Each project whether included as of the Commencement Date or subsequently added at the request of Certegy, subject to Section 9.6 of the Master Agreement, will have a plan developed (the "Project Plan") and, upon approval by both Parties, the Project Plan will be assigned a sequential number and will be attached to, and become a part of, this Schedule (e.g., Mainframe Project Plan M-1/Title, Mainframe Project Plan M-2/Title,

Appears in 1 contract

Sources: Master Agreement for Operations Support Services (Fidelity National Information Services, Inc.)

Project Management Process. IBM IBM's Project Management process is based upon the premise that the IBM Account Manager will have overall responsibility and accountability to meet all agreed upon quality, cost, schedule and technical objectives of the project. In addition, each Party will assign an individual to each project to act as its respective representative with responsibility for specific operational roles as described below and further delineated in the Project Plan ("Project Manager"). Based upon the scope of the work and the Deliverables to be provided under a project, a Project Manager may be assigned to oversee multiple Projects. Each project whether included as of the Commencement Date or subsequently added at the request of Certegy, subject to Section 9.6 of the Master Agreement, will have a plan developed (the "Project Plan") and, upon approval by both Parties, the Project Plan will be assigned a sequential number and will be attached to, and become a part of, this Schedule (e.g., Mainframe Project Plan M-1/Title, Mainframe Project Plan M-2/Title,, etc.). The terms, and conditions of the Master Agreement and the Transaction Document will apply to each project unless otherwise amended by the applicable Project Plan.

Appears in 1 contract

Sources: Master Agreement for Operations Support Services (Fidelity National Information Services, Inc.)