clement13.net
Original photo: Un dictionnaire ancien ouvert sur deux pages d'entrΓ©es et de traductions
Description
Un dictionnaire ancien ouvert sur deux pages d'entrΓ©es et de traductions
Source
auteur non indiquΓ© Β· original page
Licence
PD Public domain
Original photo, unretouched. The background is a version of it stylised by the site.

Glossary

This glossary defines more than 90 terms related to project management, development, source control, data, and BI. Each entry provides a short definition (🟒) and links…

Guideβ‰ˆ 13 min readPartly checkedPartial checkThe main facts were checked by searching the cited sources. The items below still need checking before relying on them.To re-check
  • DΓ©finitions de SAFe, DSDM, Shape Up, RUP et Merise non rouvertes sur sources primaires (dΓ©finitions classiques et stables).
Written with AI assistance; sources are cited at the bottom of the page. An error? Report it via clement13.net.
Reading
In brief

This glossary defines more than 90 terms related to project management, development, source control, data, and BI. Each entry provides a short definition (🟒) and links to the file that explores it in depth (🟑/πŸ”΄). Acronyms are listed under their usual form. When a term has variants (Scrum β€œmaster” or β€œfacilitator,” Import mode or DirectQuery), the definition uses common usage.

On this page

Level: πŸŸ’β†’πŸ”΄

A#

  • Agile β€” Family of iterative approaches based on the Agile Manifesto (2001): deliver early and often, adapt to change, collaborate with the customer. It is not a method but a mindset applied through Scrum, Kanban, XP… β†’ Agile and Lean Methods (Manifesto, Kanban, XP, Lean, Shape Up, DSDM, SAFe, DevOps…)
  • ALM (Application Lifecycle Management) β€” Management of an application's lifecycle: requirements, planning, code, testing, delivery, operations, within an integrated toolchain. Azure DevOps is a typical example. β†’ Azure DevOps Server
  • Artifact (Scrum) β€” Transparency object in the Scrum framework: Product Backlog, Sprint Backlog, and Increment, each tied to a commitment (Product Goal, Sprint Goal, Definition of Done). β†’ Scrum, the framework (Scrum Guide 2020)
  • Azure DevOps Server β€” Successor to Team Foundation Server (TFS): the on-premises installable version of Azure DevOps (work items, Git/TFVC repositories, pipelines, tests, artifacts). β†’ Azure DevOps Server (ex-TFS) in Depth
  • Partial achievement β€” Progress on a maturity milestone at 0, 0.5, or 1, which allows rating a level without requiring perfection. β†’ RATING

B#

  • Backlog β€” Ordered list of remaining work (Product Backlog: the product; Sprint Backlog: the current sprint). The order reflects value and risk, not age. β†’ Scrum in Practice
  • Big bang (delivery) β€” Go-live all at once, with no stages. Maximum risk, difficult rollback; opposite of incremental delivery. β†’ Predictive Methods (waterfall, V-model, spiral, RUP, PMBOK, PRINCE2, Merise, CMMI)
  • BI (Business Intelligence) β€” Set of techniques that transform operational data into decision indicators: warehouse, semantic model, reports. β†’ BI Development Matrix
  • Branch β€” Parallel development line in a version control system; in Git it is a simple lightweight pointer, in TFVC a logical copy of the folder. β†’ Branching Strategies
  • Burndown / burnup β€” Charts of remaining work (burndown) or completed work (burnup) over time; burnup makes scope changes visible. β†’ Project Metrics and Reporting
  • Build β€” Automated compilation and assembly step; for data, generation of a dacpac, an installation kit, or a report project. β†’ CI/CD: Continuous Integration and Continuous Delivery

C#

D#

E#

  • ELT / ETL β€” Extract, transform, load (ETL) or extract, load, transform in the target (ELT). The latter dominates with cloud engines. β†’ Data Layer and ETL
  • Epic β€” Large body of work broken down into user stories across multiple sprints. β†’ Scrum in Practice
  • Estimation (story points) β€” Relative effort assessment, not in hours; used for forecasting, not for evaluating people. β†’ Planning and Estimation (PLA)
  • Star (schema) β€” Dimensional model: one fact table surrounded by dimensions; foundation of any solid semantic model. β†’ Semantic Model
  • Eventstream β€” Fabric feature for capturing and routing real-time event streams. β†’ OneLake β€” architecture

F#

G#

  • VCS (version control system) β€” See SCM. A system that keeps file history and coordinates parallel work (Git, TFVC). β†’ Overview of Version Control Systems
  • Git β€” Distributed VCS: each clone contains the full history; lightweight branches, frequent merges. β†’ Git In Depth
  • Data governance β€” Roles, rules, and processes that ensure data ownership, quality, security, and compliant use. β†’ Data Governance and Organization
  • Gated check-in β€” TFVC control where check-in is accepted only if a build succeeds. β†’ TFVC in Depth

H#

  • Hybrid (method) β€” Deliberate combination of predictive and agile elements (waterfall framing, iterative delivery). β†’ Choosing Your Method and Hybridizing
  • Hotfix β€” Urgent fix applied to a production version, then carried over to the development branch. β†’ Branching Strategies

I#

J#

  • Milestone (maturity) β€” Precise, verifiable criterion for a matrix level, with its stable identifier (e.g., PI-RSK-3.2). β†’ RATING
  • Jira β€” Atlassian ticket and project tracking tool, highly configurable. β†’ Jira In Depth and Alternatives

K#

L#

M#

N#

  • Maturity level β€” From 1 to 5: each level describes an observable outcome, not a means. β†’ RATING
  • NFR (non-functional requirements) β€” Performance, security, availability, accessibility: often forgotten during framing. β†’ Scope and Requirements Management (PER)

O#

P#

Q#

R#

S#

T#

  • TDD β€” Test-Driven Development: write the test before the code. β†’ Testing
  • TFVC β€” Team Foundation Version Control: Microsoft’s centralized VCS, optional locks, changeset-based history. β†’ TFVC in Depth
  • Trunk-based development β€” Daily integration into a main branch, very short-lived branches. β†’ Branching Strategies

U#

  • User story β€” Need expressed from the user’s point of view, with acceptance criteria. β†’ Scrum in Practice

V#

W#

X#

See also#

✻ Written by Claude Sonnet 5.5