• Initiation
• Requirements Complete
• Commit
• Functionality Complete
• QA Complete / Release

• Project Data Sheet
• Project Plan
• External Specification
• User Requirements
• Internal Specification
• Quality Plan
• Configuration Management Plan
• Memorandum of Understanding
• Official Process Image

This Memorandum of Understanding documents the agreement between the XXX Division (XXXD) and organization (referred to as the receiving organization) regarding the use of XXXD engineering resources to work on the XXXX project.
 

Parties to the Agreement:

Parties to this agreement are:
 

name	organization	role
receiving pm	organization	ProjectManager
originating pm	XXXD	Project Manager

The engineer(s) working in this engagement is(are):
 

name	organization	role
person	XXXD	Development
person	XXXD	Development

Other contacts for this engagement are:
 

name	organization	role
person	organization	role
person	organization	role

 

Work to be Performed:

The work to be performed by the XXXD engineer(s) is: 

Description
 

Skills Necessary:

The skills required by the XXXD engineer(s) are: 

Skills
 

Duration and Deliverables:

The engagement is expected to start on start and last for length.

The expected deliverables are:
 

Deliverable	Target date
deliverable	date
deliverable	date

 

Other details (the fine print):

Other details of the engagement are:

Cost and billing: 
The receiving organization will compensate XXXD at a rate equivalent to the salary, payroll taxes and benefits for the engineer(s).  This amount is agreed to be $12,000 per month per engineer. The billing resolution will be to the nearest full day.  The XXXD will start charging the receiving organization as soon as the work commences.  Billing will occur monthly (or quarterly by arrangement) through the length of the engagement.

Logistics:
The XXXD engineer(s) will be relieved of any significant responsibilities not related to the engagement by XXXD.  The XXXD engineer(s) will continue to be physically located in the XXXD.  Any additional equipment, software, travel or training necessary for the engagement as determined by the receiving organization’s project manager(s) will be provided by, paid for, or charged to the receiving organization.  Normal, ongoing XXXD engineer development expenses will be the responsibility of the XXXD.  The XXXD project manager(s) will perform progress checks with the receiving organization on the status of the engagement at least once a month.

Changes to the deliverables:
Any changes to the deliverables will be agreed to by the originating organization’s project manager and the XXXD project manager.  The changes will be documented in writing and sent to the managers at the involved organizations and to the XXXD engineers working on the project.

Changes to the schedule:
The XXXD engineer(s) may be released from the project earlier than date depending on the status of the project as determined by the receiving division’s project manager.  The engagement may extend beyond the agreed upon date only at the mutual agreement of the receiving organization and XXXD.

Management’s role:
The receiving organization’s project manager(s) will provide the project management for the XXXD engineer(s) during the engagement.  The XXXD manager(s) will perform non-project related management activities and are responsible for evaluations and ranking, and will be available for consulting as appropriate.  The receiving organization’s project manager will provide performance feedback to the XXXD manager(s) for the XXXD engineer’s performance evaluations.

Support responsibilities: 
The receiving organization will be responsible for support of the work after the engagement.  The XXXD engineer(s) will be available for occasional consulting to support the receiving organization’s engineers after the engagement on an as-time-available basis.

Ownership of workproducts:
The XXXD provides consulting and promotes code-reuse throughout TMO, and the receiving organization will support leveraging the work elsewhere as appropriate.   The receiving organization will retain rights and control over the domain specific aspects.  This includes materials, algorithms, documentation and source code created for the project.  XXXD will support the receiving organization’s efforts to patent their domain specific technology.  XXXD will retain rights and control over common and/or reusable libraries and components (not domain specific).  The XXXD will be responsible for any additional efforts to make them more reusable (documentation, maintenance, and support).  The receiving organization will support any XXXD efforts to patent the common technology.

Testimonial:
Upon completion of the engagement, the receiving organization will provide XXXD with a short summary of the project.  This should be less than a half dozen PowerPoint slides and include an assessment of the value that XXXD provided in the engagement.  XXXD will use these materials internally to HP to build awareness of (1) the receiving organization, (2) the receiving organization’s product or project, and (3) XXXD’s skill sets.