Функциональный компонент «Проект» Project Functional Component

Простыми словами

Компонент — система записи по всем ИТ-инициативам: создаёт их по спецификациям соглашения об объёме работ, включая стоимость, сроки, объём и качество, ведёт их жизненный цикл и статус, координирует ресурсы, финансы, задачи и вехи. Отвечает на вопрос «идёт ли работа в границах одобренного», а при выходе отклонений за пороги отправляет обратную связь в поток S2P. Обязанность, которой нет больше ни у кого: держать сцепку соглашение об объёме — ИТ-инициатива — релиз услуги, на которой стоит вся прослеживаемость от бюджета до выпуска. Отличать от Proposal Functional Component потока S2P: тот владеет соглашением об объёме и решает, что одобрить, а этот исполняет одобренное и соглашением не владеет — он его получает.

Определение из первоисточника

Основные параметры

Атрибуты этой сущности по справочнику источника.

• Функциональные критерии стандарта: 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 coordinate resources, finances, tasks, and milestones for IT Initiatives, and provide ongoing execution oversight of IT Initiatives when creating new services or enhancements to existing services. Shall create IT Initiatives based on the specifications outlined in the Scope Agreement, including cost, time, scope, and quality. Shall 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. Shall govern, coordinate, influence, and direct IT Initiative execution. Shall ensure financial goals and boundary conditions are adhered to. Shall maintain traceability between IT Initiatives and associated applications and service(s) being developed. Shall maintain the linkage/traceability between Scope Agreements, IT Initiatives, and Service Releases. Shall produce various request artifacts associated with financial, human, and technology resources (that is, feedback to the S2P Value Stream when variances cross thresholds). Shall coordinate the acquisition of resources (hardware, software, and people) required to source/create a service in a particular project. Shall track spend for IT Initiatives attached to each Scope Agreement and pass it to the Service Design functional component. Can submit one or more RFCs required for the IT Initiative if a Change Control functional component exists. Can manage the Subscription data flow to the Request Rationalization functional component if a Request Rationalization functional component exists. Can send a request to the Request Rationalization functional component when resources are required for the IT Initiative if a Request Rationalization functional component exists. Shall be able to receive the Scope Agreement from the Proposal functional component if a Proposal functional component exists. Can provide IT Initiative information required for Service Design to the Service Design functional component if a Service Design functional component exists. May receive the subscribed service charges from the Chargeback/Showback functional component if a Chargeback/Showback functional component exists. May send charge acceptance to the Chargeback/Showback functional component if a Chargeback/Showback functional component exists. May receive the development scope and agreement from the Service Portfolio functional component if a Service Portfolio functional component exists. Объекты данных компонента: IT Initiative.

Связанные понятия