According to MuleSoft's IT delivery and operating model, which approach can an organization adopt in order to reduce the frequency of IT project…

According to MuleSoft's recommended IT operating model, decoupling central IT from line-of-business (LOB) innovation is crucial for reducing project failures. Central IT's role shifts to creating and governing reusable API assets (System and Process APIs). This enables LOBs to self-serve and rapidly build new experiences and applications by consuming these assets. This separation of concerns reduces the complexity and dependencies of large, monolithic projects, allowing for faster, more agile delivery with a lower risk of failure. This approach fosters an "application network" where business units can innovate independently without being bottlenecked by central IT's release cycles.

A. Adopt an enterprise data model: A rigid, enterprise-wide data model can create a bottleneck and hinder the agility that MuleSoft's API-led approach is designed to promote.

B. Stop scope creep by centralizing requirements-gathering: This describes a traditional, waterfall approach. MuleSoft's model advocates for enabling business units, not creating a central bottleneck for requirements, which often slows delivery.

D. Prevent technology sprawl by reducing production of API assets: This is counterintuitive to the MuleSoft model, which encourages the creation of a rich network of reusable API assets to accelerate, not hinder, innovation and delivery.

1. MuleSoft Whitepaper, "The new IT operating model for digital transformation": This document outlines the shift from a traditional, centralized IT model to a decentralized one. It states, "Central IT’s role is to build a foundation of assets that can be used by the rest of the business... This frees up the LOBs to focus on innovation and delivering projects that are specific to their needs." (Section: "The new IT operating model", Page 5). This directly supports the concept of decoupling central IT from LOB innovation.

2. MuleSoft Documentation, "Center for Enablement (C4E)": The C4E model is MuleSoft's framework for implementing the new operating model. It describes how Central IT acts as an enabler, providing "foundational assets, support, and expertise," which allows LOB developers to "discover and self-serve the assets they need to achieve their project goals faster." (MuleSoft Docs > Anypoint Platform > Center for Enablement). This reinforces the principle of separating the creation of core assets from their consumption for innovation.

3. MuleSoft Whitepaper, "API-led Connectivity": This paper explains how decoupling layers of APIs (System, Process, Experience) allows for parallel development and reduces dependencies. "By decoupling the user experience from the systems of record, organizations can innovate and adapt to new market demands without disrupting the underlying systems." (Section: "The benefits of API-led connectivity", Page 4). This architectural decoupling is the technical implementation of the operating model described in option C.