Centre of Excellence

Purpose

To define, evolve and embed best practice for a specific capability area (e.g. Agile, Product, Engineering, IT, InfoSec, Data) across DMG, so teams deliver work consistently, safely and effectively. A Centre of Excellence exists to reduce variation in “how we work”, raise organisational maturity over time, and make the right way the easy way. It enables, it does not execute.

• A best-practice function
• A learning and improvement engine
• A consistency enabler
• A maturity driver

• A delivery team
• A sign-off authority for day-to-day work
• A bottleneck
• A centralised decision maker

Output

The CoE produces organisational assets, not delivery artefacts:

• Standards & principles (the agreed way to do things)
• Guidelines & playbooks (how to apply the standards in practice)
• Patterns & examples (reusable, proven approaches)
• Capability uplift (shared understanding and confidence)
• Clear guardrails (what is mandatory vs flexible)

These outputs are consumed by teams, embedded into ways of working, and evolve over time.

Input

• Recurring problems and inconsistencies across teams
• Lessons learned from real work
• New regulatory, security or compliance requirements
• Changes in strategy, scale or technology
• Requests for guidance (“we keep hitting this problem — what's the right approach?”)

The CoEs

• Agile CoE — defines how teams plan, estimate, improve and collaborate
• Product CoE — defines how problems are discovered, shaped and prioritised
• Engineering CoE — defines how software is built, tested and maintained
• IT CoE — defines how services are run reliably and sustainably
• InfoSec CoE — defines how risk is managed and security is built-in by design
• Data CoE — defines how data is defined, governed, protected and trusted

Attendees

• CoE Owner(s)
• Domain SMEs (Agile / Product / Engineering / IT / InfoSec / Data)
• Practitioners from the domain / interested participants

Responsibilities

• Owns what good looks like for the capability (e.g. Agile maturity, secure-by-design, data quality, engineering standards, product discovery quality)
• Owns the standards, principles and guardrails for the domain
• Prioritises improvement themes based on organisational need, risk and feedback
• Ensures standards align to business strategy, regulatory needs and technology direction

• Runs the CoE cadence as a community of practice
• Facilitates learning, discussion and shared problem-solving
• Surfaces systemic issues and recurring pain points across teams
• Turns insight into improvement backlog items (standards, guidance, patterns)