The distinct ownership and governance requirements introduced by agnostic services can introduce the

Question

Options

• Amanagement-centric, administration-centric
• Bdevelopment-centric, quality assurance-centric
• Centerprise-centric, project-centric
• Ddevelopment-centric, communication-centric

• A
  16% (6)
• B
  3% (1)
• C
  73% (27)
• D
  8% (3)

Explanation

Option C is correct because agnostic services - designed to be reusable across multiple contexts - inherently serve two competing masters: the enterprise (which owns and governs the shared service as a broad organizational asset) and individual projects (which consume the service and have their own timelines, requirements, and priorities). This dual accountability creates inherent governance tension that doesn't exist with non-agnostic, purpose-built services.

• A (management/administration-centric) is wrong because these two terms describe similar administrative functions rather than the distinct ownership layers that agnostic services introduce.
• B (development/QA-centric) is wrong because these refer to software delivery phases, not governance or ownership structures.
• D (development/communication-centric) is wrong because communication is not a recognized ownership domain in service governance frameworks.

Memory tip: Think of the acronym EP - agnostic services must satisfy both the Enterprise (who funds and maintains them) and the Project (who uses them), and those two groups rarely want the same things at the same time.

No community discussion yet for this question.