HR Agile & Project Management Glossary
Agile and project-management terminology is the vocabulary of how modern delivery teams actually work — and, increasingly, of how HR and talent teams run their own programmes and hire for the roles that run these ways of working. This topic gathers the Agile, SAFe, and project-management terms most relevant to talent acquisition and Global Capability Centres, each defined on its own page.
For recruiters and HR leaders, this matters on two levels. GCCs staff Scrum Masters, Product Owners, and Release Train Engineers by the hundred, so understanding what these roles genuinely involve — beyond a certificate — is central to assessing them. And the same disciplines are worth borrowing: running hiring in sprints, visualising a pipeline on a Kanban board, or bringing PMO-style governance and a RACI to a GCC set-up all apply the delivery playbook to People work. The terms here span both the Agile ceremonies and roles and the classic project-management concepts — critical path, work breakdown structure, scope creep — that large HR programmes depend on.
Each term is framed with the talent and GCC lens rather than as pure software theory — what it means for hiring, for the roles a centre recruits, and for running People programmes at scale.
26 terms in this topic · see all 277 in the A–Z glossary →
Terms 26
Agile HR Agile HR is the application of agile principles — short cycles, cross-functional teams, continuous feedback, and iteration over up-front planning — to the way People and HR functions work. Instead of running annual, waterfall-style programmes, agile HR teams deliver in small increments, test what works, and adapt fast to changing workforce needs. Read Agile Release Train ART An Agile Release Train (ART) is a long-lived team of agile teams — typically 50 to 125 people — that plans, commits, and delivers together on a common cadence in the Scaled Agile Framework (SAFe). All the teams on the train align to shared objectives and a single planning rhythm, so a large group can deliver value as one coordinated whole. Read Change Request A change request is a formal proposal to alter something already agreed on a project — its scope, schedule, budget, or requirements — so that the change can be assessed, approved or rejected, and recorded rather than absorbed silently. It is the control mechanism that keeps changes deliberate instead of letting a project drift. Read Critical Path The critical path is the longest sequence of dependent tasks in a project — the chain that determines the shortest possible time to finish. Any delay to a task on the critical path delays the whole project, which is why these tasks get the closest management attention. Read Cross-Functional Team A cross-functional team is a team that contains all the different skills needed to deliver an outcome end to end — rather than being grouped by a single function — so it can complete work without depending on other teams. In agile organisations this typically means engineers, designers, testers, and product people working together as one unit. Read Daily Stand-up A daily stand-up is a short, time-boxed meeting — usually 15 minutes — in which an agile team synchronises each day on progress towards the sprint goal and surfaces anything blocking it. It is called a stand-up because keeping people on their feet helps keep it brief and focused. Read Gantt Chart A Gantt chart is a horizontal bar chart that shows a project’s tasks along a timeline, with each bar representing when a task starts, how long it lasts, and how it overlaps or depends on others. It gives an at-a-glance view of a schedule — what is happening when, and what must finish before something else can begin. Read Kanban Kanban is an agile method for managing work as a continuous flow, using a visual board of columns (such as To Do, In Progress, and Done) and limits on how much work can be in progress at once. Unlike Scrum, it has no fixed sprints — work is pulled through the board as capacity frees up, and delivery is continuous. Read Milestone A milestone is a significant checkpoint in a project that marks the completion of a major phase or deliverable — a fixed point used to track progress rather than a task with duration. Milestones such as “entity incorporated” or “first cohort onboarded” give a project measurable markers of whether it is on schedule. Read Product Backlog A product backlog is a single, ordered list of everything that might be built or improved for a product — features, changes, fixes, and requirements — kept in priority order so the team always knows what is most valuable to do next. It is the definitive source of the work an agile team draws from, owned and prioritised by the Product Owner. Read Product Owner PO A Product Owner is the person accountable for maximising the value a Scrum team delivers, principally by owning and prioritising the product backlog. They decide what the team builds and in what order, translating customer and business needs into a clear, ranked list of work — and they are the single point of decision on scope and priority. Read Program Increment Planning Program Increment (PI) Planning is a large, recurring event in the Scaled Agile Framework where all the teams on an Agile Release Train plan together for the next Program Increment — usually eight to twelve weeks of work. Over one or two days the teams align on shared objectives, map cross-team dependencies, and commit to a plan as a single group. Read Project Charter A project charter is a short, formal document that authorises a project and sets out its purpose, objectives, scope, key stakeholders, and the authority of its manager. It is the agreement, signed off by the sponsor, that a project should exist — the reference point everyone returns to when questions of scope or intent arise. Read Project Kickoff A project kickoff is the meeting that formally starts a project, bringing the team and key stakeholders together to align on its purpose, scope, roles, plan, and ways of working before delivery begins. A good kickoff sets shared expectations and momentum; a poor or skipped one leaves people working from different assumptions. Read Project Management Office PMO A Project Management Office (PMO) is the central team or function that defines and maintains how projects are run across an organisation — setting standards, tools, and governance, and often overseeing the portfolio of projects. In HR and GCC settings, a PMO brings consistency and reporting to large programmes such as a centre set-up, an HR transformation, or a mass-hiring drive. Read RACI Matrix A RACI matrix is a simple grid that clarifies who does what on a project by assigning each task or decision one of four roles: Responsible (does the work), Accountable (owns the outcome), Consulted (gives input), and Informed (kept in the loop). It prevents confusion by making explicit who owns a decision and who merely contributes to it. Read Scaled Agile Framework SAFe The Scaled Agile Framework (SAFe) is a set of practices for applying agile and lean methods across many teams working on the same large product or portfolio. It coordinates multiple agile teams — often dozens or hundreds of people — through shared planning cadences and structures such as the Agile Release Train, so a whole organisation can stay aligned while still working in an agile way. Read Scope Creep Scope creep is the gradual, uncontrolled expansion of a project’s scope after it has begun — new features, requirements, or requests added without matching adjustments to time, budget, or resources. Because each addition seems small, the growth often goes unnoticed until the project is late, over budget, or unable to deliver. Read Scrum Scrum is an agile framework for delivering work in short, fixed-length cycles called sprints, using a small cross-functional team, a prioritised backlog, and a set of regular events to inspect progress and adapt. It is the most widely used way of organising agile software teams — and the roles and rituals GCCs most commonly hire for. Read Scrum Master A Scrum Master is the person accountable for helping a Scrum team work effectively — facilitating its events, coaching it on agile practices, and removing the obstacles that slow it down. The role is a servant-leader and enabler, not a project manager or boss: the Scrum Master serves the team rather than directing it. Read Sprint A sprint is a short, fixed-length cycle — typically one to four weeks — during which an agile team completes a set amount of work and produces a usable increment. Sprints give delivery a steady rhythm: the team plans at the start, works through the sprint, then reviews the result and reflects before the next one begins. Read Sprint Retrospective A sprint retrospective is a meeting held at the end of each sprint in which the team reflects on how it worked — what went well, what did not, and what to change — and commits to a small number of concrete improvements for the next sprint. It is the mechanism through which an agile team gets better at working, not just at delivering. Read Stakeholder Management Stakeholder management is the practice of identifying everyone affected by or able to influence a project, understanding their interests and influence, and engaging them appropriately so the project has the support it needs to succeed. It is the deliberate work of keeping the right people informed, consulted, and on side. Read User Story A user story is a short, plain-language description of a feature or need told from the point of view of the person who wants it, typically in the form “As a [user], I want [something] so that [benefit].” It captures what a user needs and why, leaving the detailed how to a conversation between the team and the Product Owner. Read Waterfall Model The waterfall model is a traditional, sequential approach to project delivery in which work flows through distinct phases — such as requirements, design, build, test, and deployment — one after another, with each phase completed and signed off before the next begins. It contrasts with agile, which delivers iteratively rather than in one linear pass. Read Work Breakdown Structure WBS A work breakdown structure (WBS) is a hierarchical breakdown of a project into progressively smaller pieces, from the overall goal down to the individual deliverables and tasks needed to achieve it. Decomposing the work this way makes a large, vague project estimable, assignable, and trackable. ReadFrequently asked questions
Why should HR and recruiters understand Agile terminology?
Because GCCs staff Agile roles — Scrum Masters, Product Owners, Release Train Engineers — by the hundred, and assessing them well means understanding what the roles genuinely involve beyond a certificate. HR teams also increasingly borrow Agile ways of working for their own programmes.
What is the difference between Scrum and Kanban?
Scrum organises work into fixed-length sprints with set roles and ceremonies, while Kanban manages a continuous flow using a board and work-in-progress limits, with no sprints. Scrum is iterative; Kanban is flow-based; many teams blend the two.
Which project-management terms matter most for HR programmes?
For running HR and GCC programmes, the key concepts are the critical path, work breakdown structure, milestones, RACI (who is responsible and accountable), scope creep, and stakeholder management — the tools that keep a large, multi-workstream effort on track.
Can HR teams use Agile methods themselves?
Yes. People and talent teams run hiring in sprints, visualise pipelines on Kanban boards, and hold retrospectives to improve — applying the same delivery discipline that engineering teams use to their own work.
Explore further
Other topics
Compensation & BenefitsRecruitment & Hiring MetricsGCC Operating ModelsHR Mental ModelsSourcing & Candidate AttractionInterviewing & AssessmentTalent Management & DevelopmentOnboarding & Employee LifecycleContingent & Global EmploymentUS Employment Law & ComplianceEmployee Experience & EngagementHR Operations, Roles & AnalyticsRecruitment Models & Search TypesExits, Separation & Redundancy