NOTICE: Branded Content
NOTICE: Certain versions of content (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.
IT4IT™ Value Chain Forum
cancel

Applying the IT4IT Reference Architecture to the area of Agile and DevOps

eranc Absent Member.
Absent Member.

Applying the IT4IT Reference Architecture to the area of Agile and DevOps

We often get the question of how does the IT4IT framework relates to the Agile and DevOps. Given the reference architecture’s complexity and terms used (i.e. “requirement” vs. “product backlog item”), it may not be obvious from a first glance. However, as the IT4IT framework is process and methodology agnostic, it can most definitely support Agile and DevOps. The intent is to enable loosely-coupled, decentralized agile teams by prescribing simple IT coordination interfaces supporting accepted agile implementation patterns, resulting with end-to-end traceability of IT services.

The published Agile Scenario Document in The open Group IT4IT forum explains how the IT4IT reference architecture is used to enable multiple scenarios:

  1. Portfolio Backlog Scenario - Demonstrates how portfolio backlogs are managed in a consistent way by recording portfolio backlog items, validate against exiting services or create new ones, and map portfolio backlog items to product backlog items (see next scenario). This scenario is focused in the S2P domain with a touch point to R2D.
  2. Product Backlog Scenario - Demonstrates how product backlogs are managed in a consistent way by recording product backlog items such as requirements (“user stories”), defects and known errors, as well as enabling traceability with the service release. This scenario is focused in the R2D domain, with a touch point to D2C.
  3. DevOps and Automation Scenario - Demonstrates how software is built, deployed, tested and delivered continuously, by leveraging automation and traceability between entities. This scenario is focused in the R2D domain, with touch points to R2F and D2C.

Another resource which supports Agile and DevOps in IT4IT is the published R2D Concept and Configuration Guide found in the R2D page in the Solutions Portal. It includes two types of use cases:

  1. Service development and delivery using a combination of both agile and non-agile development of the underlying components.
  2. DevOps use cases such as build software, deploy to dev/test and deploy to staging/production.