Open Group IT4IT Reference Architecture Project Component

​Purpose

• Coordinate the creation and provide ongoing execution oversight of IT Initiatives aimed at the creation of new or enhancements to existing services.
• Create IT Initiatives based on the specifications outlined in the Scope Agreement, including cost, time, scope, and quality.
• Aggregate, track, and report status, resources consumed against project plan, or project burn down, and communicate these to stakeholders via auxiliary functional components such as Resource Management, Supplier Management, and IT Financial Management.
• Govern, coordinate, influence, and direct initiative execution.
• Ensure financial goals and boundary conditions are adhered to.
• Maintain the connection between initiatives and associated applications and service(s) being developed.
• Maintain the linkage/traceability between Scope Agreements, IT Initiatives, and Service Releases.
• Produce various request artifacts associated with financial, human, and technology resources (that is, feedback to the S2P Value Stream when variances cross thresholds).
• Coordinate the acquisition of resources (hardware, software, and people) required to source/create a service in a particular project.

Main Functions

The Project functional component:

• Shall be the system of record (authoritative source) for all IT Initiatives.
• Shall manage the lifecycle of the IT Initiative.
• Shall manage the status of the IT Initiative.
• Shall allow recursive relationships between IT Initiatives.
• Shall associate an IT Initiative to a service.
• May associate an IT Initiative with IT budget in the IT Financial Management supporting function.
  

If a Change Control functional component exists, the Project functional component:

• Shall associate an IT Initiative to one or more RFCs.
• Can submit one or more RFCs required for the IT Initiative.
  

If a Fulfillment Execution functional component exists, the Project functional component:

• Can manage the Fulfillment Request data flow to the Fulfillment Execution functional component.
• Can send a request to the Fulfillment Execution functional component when resources are required for the IT Initiative.
  

If a Proposal functional component exists, the Project functional component:

• Shall associate a Scope Agreement to one or more IT Initiatives.
• Shall be able to receive the Scope Agreement from the Proposal functional component.
  

If a Service Design functional component exists, the Project functional component:

• Can provide IT Initiative information required for Service Design to the Service Design functional component.