A project often fails for a simple reason: the people around the table do not understand the same thing by the same word. PMO, RAG, FinOps, data mesh, SRE: these acronyms circulate in committees without their meaning always being shared.
Why a glossary
This glossary has a modest but useful ambition: to give each term a short, accurate definition that a non-specialist can read. It covers the terms that come up in AI, data, cloud and project management projects.
Each entry follows the same structure. It opens with a two-sentence definition that you can reuse as it stands in a note or a presentation. It then explains what the notion is for, what its variants are and which related terms it is confused with. It ends with a concrete example.
The domains covered
The entries are divided between our five areas of expertise.
- Project management: project office, portfolio management, frameworks and certifications, forms of organisation.
- Artificial intelligence: language models, retrieval-augmented generation, agents, European regulatory framework.
- Data: platform architectures and model industrialisation.
- Cloud and platforms: reliability, cost control, platform engineering, texts on resilience and security.
- Software engineering: technical debt.
How we handle regulatory texts
Entries devoted to a regulation or a directive cite the text by its official reference. They describe its purpose and its main principles, without replacing a legal analysis of your situation. Precise deadlines and obligations depend on your business: check them with your legal department or the competent authority.
Further reading
Each entry links to the related terms and to the corresponding service among our expertise. For more in-depth analysis, see our insights.