top of page

Manifesto for Enterprise Agility: A Corporate Agility Guide for Large-Scale ERP/CRM Projects

Manifesto for Enterprise Agility: A Corporate Agility Guide for Large-Scale ERP/CRM Projects
Manifesto for Enterprise Agility: A Corporate Agility Guide for Large-Scale ERP/CRM Projects

PMI’s new Enterprise Agility Manifesto positions “enterprise agility” in a different place than team-level agility: the capacity to align at scale and adapt to change without losing coherence. The manifesto’s definition highlights the focus on management and leadership in particular; it frames agility not merely as speed, but as the ability for strategy to turn into action under real-world pressure.


In corporate transformation projects, the concept of “agility” had long tended to be read as synonymous with team-level practices (Scrum cadence, sprint, backlog). PMI’s new Enterprise Agility Manifesto, however, addresses agility from a higher level—from the level of the management system: the capacity to adapt to change at scale and to convert strategy into action under real-world pressure.


This approach is especially critical for large projects. Because an end-to-end ERP/CRM transformation encompasses process, data, integration, regulation, and the human factor simultaneously. At this scale, success is possible not only with “the right configuration,” but with the right governance, the right funding, and the right decision-rights architecture.


When we come to large-scale ERP/CRM projects, the critical inference is this: the manifesto does not confine “agile management” to a sprint cadence; it calls for the main rupture in the governance model (guardrails vs. gatekeepers), in the financing logic (intent/outcome-focused funding), and in decision rights (bringing them closer to where value is created). This emphasis points to a “hybrid/fit-for-purpose” model that aligns with the nature of large-scale projects, which inherently carry a high load in integration, regulation, and change management.


In the context of Turkey, three additional layers become distinct:

  1. Macroeconomic volatility (inflation), due to the limited predictability of budgeting and procurement cost dynamics, makes the “fixed plan + fixed budget” approach more fragile.

  2. Regulatory intensity (KVKK’s cross-border transfer regime; e-document/e-ledger obligations; EU CBAM reporting burdens) must be systematically embedded into the backlog of large-scale projects as “compliance requirements.”

  3. Executive–execution gap: the manifesto already quantitatively points to barriers such as “leadership mindset/resistance” and “planning–execution disconnect”; in Turkey, the limited increase in digital transformation maturity, as well (the TÜBİSAD index), provides a contextual signal that this gap is a persistent governance problem.


Summary of the Manifesto: Definition, Values, and Principles

The manifesto defines enterprise agility as “adapting at scale without losing coherence; making decisions quickly; deliberately redirecting resources; keeping strategy actionable.”


The methodology shared by PMI shows that there is a mixed-method research behind the manifesto: it consists of C-suite surveys with 700+ responses, 30+ C-suite interviews, 70+ practitioner inputs, and a synthesis of 49 frameworks/academic sources. This diversity shows that the manifesto is positioned methodologically rather than being merely a “statement of opinion.”


The manifesto is built on four core values and nine principles. Below, how these values and principles are reflected in ERP/CRM projects is summarized, and critical points are discussed in the context of Turkey’s conditions (high inflation, frequent regulation, gaps in implementation). Finally, a six-step implementation roadmap is presented.


Four Values and Their Descriptions

The following translations are kept concise, remaining faithful to the wording of the manifesto.


Orijinal Manifesto

Means

Clear purpose realized through adaptive plans

Reaching a clear goal through flexible plans. For example, in SAP projects, scope is adapted through fit-to-standard workshops while the purpose is preserved.

Shared enterprise outcomes over functional optimization

Organizational outcomes (e.g., customer satisfaction, business cycle time) are taken as the basis instead of department KPIs. Funding is also planned according to these outcomes.

Continuous reinvention over preservation

Continuous innovation rather than preserving the status quo; in the SAP system, continuous release and improvement cycles are established. Courage for innovation is emphasized.

Human centricity amidst change

Bringing user experience, team trust, and learning to the forefront rather than focusing on process and technology. Supported with empathy and training even during crisis moments.


Within the same page, the framing that appears as the “comment line” of the values also supports the aspects of agility, such as “adjusting along the way” and “going beyond organizational boundaries.”


Within this values framework, the manifesto explicitly states that “purpose-driven steering over the illusion of excessive planning and control, enterprise goals over department KPIs, courage for innovation over structural inertia, and empathy-learning over process obsession should come to the fore.” In short, the vision is stable; plans are flexible.


The Nine Principles

The manifesto divides nine principles into three sub-clusters: Leadership Behavior, Organization Design, and Execution.


Cluster

Original Manifesto

Leadership Behavior

Create clarity of purpose and align on enterprise outcomes

Leadership Behavior

Expand agility across partners and ecosystems

Leadership Behavior

Embrace technology and distributed talent

Organization Design

Govern with clear guardrails, not gatekeepers

Organization Design

Fund purpose and intent, not execution activity

Organization Design

Design for adaptability, not just efficiency

Execution

Move authority and decision-making to where value is created

Execution

Deliver value frequently and make work visible

Execution

Sense early, learn quickly, act with confidence

According to the manifesto’s research data, issues such as leadership resistance and a “planning–execution” disconnect are quite widespread. These principles, therefore, play a critical role in ERP/CRM projects as well as for the topics addressed in the continuation of the work.


Methodology and the “Why Now” Argument

PMI’s manifesto page lists the methodology clearly: two C-suite surveys with 700+ responses; 30+ C-suite interviews; a survey of 70+ senior practitioners; a desk synthesis in September 2025 of 49 manifestos/frameworks/academic sources; and a public feedback board.


In the “Why now?” section, references are used, such as the proportion of CEOs emphasizing the need to rethink the business model at regular intervals, “time/energy scarcity,” and erosion of trust in leadership.


Critical Impacts for ERP Projects

Large ERP/CRM projects are the “stress test of enterprise agility”: integration, data transformation, business process alignment, regulation, and organizational change are managed simultaneously. The ERP critical success factors literature shows recurring axes such as top management support, clear vision, change management, and process management.


Reading the manifesto’s nine principles by translating them into the project context archetypes of “governance–funding–decision rights–delivery cadence” is more efficient.


Governance: How Does the “Guardrails” Approach Work in ERP/CRM Projects?

The PMI manifesto says, “Gatekeeping (gatekeeper—this can also be called micromanagement) increases risks.


A “gatekeeper” type of governance (heavy approval gates, delayed decisions) increases cost and schedule risks in projects, because integration debt accumulates when dependencies are not made visible early. The manifesto instead proposes accelerating through “clear guardrails” (standards, decision boundaries, risk tolerance, data/integration principles).


Guardrails mean speed through frameworks such as architecture and data standards, security principles, and compliance requirements. For example, in SAP projects, the clean core principle (using the core SAP code without customization) is a full guardrail. This approach is aligned with the fit-for-purpose/hybrid project management literature: hybrid approaches become critical in practice due to different organizational cultures, contractual requirements, and process specificities.


Funding: How Does “Purpose and Intent” Focus Reframe the Project Budget?

The manifesto says, “Fund purpose and intent, not execution activity.” In other words, by suggesting funding “purpose/intent” rather than “execution activity,” it says: invest not in what you do, but in why you do it. In project management, this requires moving from “module-based project budget” to a portfolio logic such as value stream/business outcome-based investment (e.g., “reducing the Order-to-Cash cycle time,” “compliant e-document flow,” “inventory accuracy”). To give a simpler example, instead of “installing a new module,” investment is made in the objective of “reducing the processing time of the entire business process by 20%.”


This logic matches approaches that bring strategy–investment–governance together in frameworks such as agile portfolio management and lean portfolio management. In addition, the Beyond Budgeting approach is discussed in the literature as a governance alternative that reduces centralization and emphasizes adaptive management processes.


Decision Rights: Which Decisions Move “To Where Value Is Created,” and Which Do Not?

The manifesto says, “Move decision rights to where value is created.” In large projects, leaving all decisions “to the teams” is not realistic; data security, regulation, and architectural integrity require certain centralized decisions. To adapt the manifesto sentence to large ERP/CRM projects in a healthy way, it is necessary to divide decisions into three:


  • Central principle decisions: data classification/access, integration standards, “clean core” principles, regulatory compliance policies.

  • Productized process decisions: fast decisions in fit-to-standard workshops together with process owners. SAP Activate’s fit-to-standard approach aims for this acceleration.

  • Daily delivery decisions: within-sprint design, configuration, test data/automation, small-scope decisions.


In the SAP ecosystem, the “clean core” approach aims to facilitate upgradability and continuous transformation by keeping the core lean; this forms a natural package with “govern with guardrails.”


Delivery Cadence and Visibility: Is “Frequent Value Delivery” Realistic in ERP?

The manifesto says, “Deliver value frequently and make work visible.” In ERP/CRM, “value” is not always a function released to production; sometimes intermediate outputs such as a validated data migration wave, a completed integration contract, or an e-document flow that passes compliance tests are also “preconditions of value.” Therefore, it is necessary to consider the definition of “value” together with the gating criteria (Definition of Done + hypercare readiness).


A recent study on ERP/CRM project documentation shows that in agile practices, “dialogue-based, throwaway documents” have increased; however, at the end-to-end project scale, the need for search/traceability continues. This finding supports that the principle of “making work visible” requires not only a sprint board in projects, but also decision logs and a traceable information architecture.


ERP/CRM Project Risks: How Do Manifesto Principles Change Risk Management?

Risks in large ERP/CRM projects usually cluster around:

  1. scope and customization debt,

  2. integration and data quality,

  3. user adoption,

  4. regulatory compliance,

  5. vendor/contract management.


The critical success factors literature for large-scale projects repeats the “governance” roots (top management, change, process) of these risks.


Aşağıdaki tablThe table below provides a “risk–countermeasure” reading by linking manifesto principles directly to ERP/CRM project management practices.


Manifesto ilkesi

Practical counterpart in ERP/CRM projects

Typical risk if neglected

ERP/CRM-aligned countermeasure

Guardrails, not gatekeepers

Architecture/data security standards + fast decision forums

Decision delays, scope creep, integration debt

Architecture guardrails + fast design workshops (fit-to-standard)

Fund purpose/intent

Value-stream-based investment, outcome KPI

“Lots of activity, little output” syndrome

Portfolio OKR/KPI + value-based roadmapping

Move decision rights

Clarity of process ownership & product ownership

C-level escalation overload

Decision matrix (RACI/DRI) + decision latency measurement

Deliver frequently, visible work

Wave-based data/integration deliveries, transparent risk logs

“Big bang” surprises, late testing

Integrated test sprints + visible dependency map

Sense early, learn quickly

 Early signals: user feedback, performance, compliance

Late-detected process misalignment

Telemetry + checkpoints + hypothesis testing


Turkey Context: Macro Conditions, Regulation, and Implementation Gap


Macro Volatility and the Budget Reality

In Turkey, inflation indicators create “predictability” pressure in terms of program budgeting and procurement costs. In the e-Devlet summary based on TÜİK’s February 2026 bulletin, the annual CPI is reported as 31.53%. The Central Bank’s Inflation Report page also shows that policymakers share the outlook with a regular reporting regime.


Under these conditions, the “annual fixed budget–fixed scope” approach in ERP/CRM projects should be consciously reconsidered in light of the manifesto’s “adaptive plans” and “fund intent” principles.


KVKK and Cross-Border transfer: the governance load of cloud/integration architecture

KVKK has clarified the “appropriate safeguards” framework for cross-border data transfers; it has incorporated the mechanisms of standard contractual clauses and binding corporate rules into corporate practice. KVKK’s “Cross-Border Transfer” page and the relevant guide contextualize transfer mechanisms and Board decisions.


In ERP/CRM projects, this requires embedding the triad of data inventory + data classification + transfer contracts into “program management,” especially in cloud components, global support operations, and third-party integrations. This is a very concrete counterpart of the manifesto’s “guardrails” principle in Turkey.


E-document/e-ledger and Official Gazette communiqués: must be embedded into the ERP/CRM backlog as “compliance items”

The e-invoice/e-archive e-document regime is defined by Tax Procedure Law communiqués; the communiqué no. 509 is accessible. In addition, communiqué no. 589, which amends no. 509 has also been published as a PDF via the Revenue Administration.


Such regulations generate compliance work in ERP/CRM projects that is costly to “catch up later.” The manifesto’s “deliver frequently and make work visible” principle, in the Turkey context, makes it mandatory for compliance tests (schematron, package format, reporting) to be visible early and continuously.


EU CBAM and sustainability reporting: the new external “regulator” face of the ERP data model

The Ministry of Trade presentation explains burdens such as reporting embedded emissions in the CBAM transition period and the methodological framework. Such burdens make the “reporting and data lineage” capabilities of ERP and CRM strategic, especially in sectors with strong exports to the EU; the manifesto’s “shared enterprise outcomes” and “sense early” principles turn into an operational value stream through sustainability compliance in Turkey.


Executive implementation gap: global finding + Turkey’s digitalization metric

On PMI’s page, among interviewed leaders, “leadership mindset/resistance” is reported as a significant barrier; “planning–execution disconnect” is also identified as a critical challenge. In Turkey, the TÜBİSAD index (2025) on digital transformation maturity reports a level of 3.13 out of 5 and indicates an area that still needs stronger momentum.


When you read these two data sets together, the argument that the success of ERP/CRM projects is an operating-system matter rather than purely technical becomes stronger: the manifesto already emphasizes “operating model” and “execution governance” for this reason.


Actionable Recommendations and the Six-Step Roadmap

This section proposes an implementation sequence that “operationalizes” the manifesto’s principles at the ERP/CRM project level. The framework is designed to be fit-for-purpose in alignment with the hybrid project management literature.


Six-step implementation sequence


Enterprise Agility Roadmap in ERP/CRM Projects
Enterprise Agility Roadmap in ERP/CRM Projects

Step 1 — Map the enterprise outcome and make it measurable. Translate ERP/CRM projects from module deliverables into the language of “enterprise outcomes” (e.g., closing cycle time, order cycle time, compliant e-document rate). This is the starting point of the manifesto’s “enterprise outcomes” alignment principle.

Step 2 — Publish the guardrails set: clean core + data/integration + compliance. Like SAP’s Clean Core approach, it feeds the guardrails logic with the aim of keeping the core lean and facilitating continuous transformation. For Turkey, the KVKK transfer regime and e-document requirements must be embedded into the guardrails set.

Step 3 — Establish the decision-rights architecture: “who decides within which boundary?” Make the manifesto’s “move authority” principle tangible with a decision matrix: process design/configuration decisions, architectural exception decisions, and compliance decisions should be separated.

Step 4 — Shift funding to an outcome/intent basis: create a portfolio cadence. The lean portfolio management approach addresses investment funding with the triad of strategy, operations, and governance. The Beyond Budgeting literature also argues that adaptive management processes should be established with the rhythm of work rather than an “annual calendar.”

Step 5 — Align the delivery cadence with ERP/CRM project reality: fit-to-standard + wave deliveries. SAP Activate and fit-to-standard reshape the blueprint to increase scope and decision speed. Within this cadence, “value delivery” must include data/integration/compliance deliveries as much as production releases.

Step 6 — Build an early sensing & fast learning system: visible work, visible risk, visible decisions. The finding about the “dialogue-based” transformation of documentation does not reduce the need for visibility; on the contrary, the findability of the right information becomes critical.


References:


Comments

bottom of page