| User Story | A description of a feature from the perspective of an end user |
| Sprint Review | A meeting at the end of a sprint to inspect the work done and adapt the product backlog |
| Pair Programming | A technique where two programmers work together at one workstation |
| Agile Values | The four core values outlined in the Agile Manifesto |
| Agile Contract | A contract designed to accommodate changes in scope and requirements through the project lifecycle |
| Value Stream Mapping | A lean-management method for analyzing the current state and designing a future state for the series of events that take a product from concept to delivery |
| Big Room Planning | A method of planning used in Agile and hybrid environments where multiple teams gather to plan and coordinate work |
| Scaled Agile | Implementing Agile practices in large, multi-team environments |
| Timeboxing | Allocating a fixed, maximum unit of time for an activity |
| Product Owner | The person responsible for defining the features of the product and prioritizing the backlog |
| Continuous Delivery (CD) | An approach where teams produce software in short cycles, ensuring it can be reliably released at any time |
| Kanban | A visual management method for controlling and optimizing workflows |
| Burn-up Chart | A visual representation of work completed versus time |
| Iteration | A time-boxed period similar to a sprint, used in Agile methodologies |
| Agile Coach | A person who helps teams and individuals adopt Agile practices and improve their processes |
| Story Points | A unit of measure for expressing the overall size of a user story or feature |
| Lean-Agile Mindset | A combination of beliefs, assumptions, and actions of leaders and practitioners who embrace the concepts of the Agile Manifesto and Lean thinking |
| Velocity | The amount of work a team can complete during a single sprint |
| Scrum of Scrums | A technique to scale Scrum up to large groups of people |
| Agile Metrics | Measurements used to assess the progress, performance, and quality of Agile projects |
| Scrum Master | A facilitator for an Agile development team |
| Daily Standup | A daily meeting for the team to discuss progress and obstacles |
| WIP Limit | A restriction on the number of work items in progress at any given time |
| Agile Project Charter | A document that outlines the vision, objectives, and stakeholders for an Agile project |
| Agile Principles | The twelve guiding principles outlined in the Agile Manifesto |
| Servant Leadership | A leadership philosophy in which the leader's main goal is to serve the team |
| Scaled Agile Framework (SAFe) | A set of organization and workflow patterns for implementing Agile practices at an enterprise scale |
| Agile Framework | A specific set of practices and principles used to implement Agile methodologies |
| Refactoring | The process of restructuring existing code without changing its external behavior |
| DevOps | A set of practices that combines software development and IT operations to shorten the development lifecycle |
| Scrum | An Agile framework for developing, delivering, and sustaining complex products |
| Waterfall Model | A sequential project management methodology with distinct phases |
| Agile Roadmap | A high-level visual summary that maps out the vision and direction of an Agile product over time |
| Agile Mindset | A way of thinking that embraces Agile values and principles |
| Burn-down Chart | A visual representation of the amount of work left to do versus time |
| Iteration Planning | A meeting in which the team plans the work to be done during the iteration |
| Increment | A functional, deliverable piece of the product that adds to previous increments |
| Sprint Planning | A meeting where the team decides what work will be performed in the upcoming sprint |
| Definition of Done | A shared understanding of what it means for work to be complete |
| Continuous Integration (CI) | A practice where code changes are automatically built, tested, and integrated into a shared repository |
| Behavior-Driven Development (BDD) | A software development approach that involves examples written in a way that describes the behavior of the application |
| Hybrid Project Management | A combination of traditional and Agile project management methodologies |
| Minimum Viable Product (MVP) | A product with just enough features to satisfy early customers and provide feedback for future development |
| Sprint | A time-boxed period during which a Scrum team works to complete a set amount of work |
| Product Backlog | An ordered list of everything that is known to be needed in the product |
| Continuous Improvement | The ongoing effort to improve products, services, or processes |
| Agile | A methodology based on iterative development where requirements and solutions evolve through collaboration |
| Backlog Grooming | The process of reviewing and prioritizing the backlog items |
| Test-Driven Development (TDD) | A software development process that relies on the repetition of a very short development cycle |
| Lean | A methodology focused on delivering value to the customer and eliminating waste |
| Epic | A large user story that can be broken down into smaller stories |
| Agile Manifesto | A declaration of four fundamental values and twelve principles to guide Agile project management |
| Agile Ceremonies | Structured meetings in Agile methodologies, including sprint planning, daily standups, sprint review, and sprint retrospective |
| Agile Adoption | The process of implementing Agile practices and principles in an organization |
| Agile Release Train (ART) | A long-lived team of Agile teams, which incrementally develops, delivers, and operates one or more solutions in a value stream |
| Agile Estimation | The process of estimating the effort required to complete work items in an Agile project |
| Cross-Functional Team | A group of people with different functional expertise working towards a common goal |
| Feature | A service that fulfills a stakeholder need |
| Sprint Retrospective | A meeting after the sprint review to discuss what went well, what didn’t, and how to improve |
| Self-Organizing Team | A team that manages its own work and collectively takes responsibility for decisions |
| Agile Transformation | The process of transitioning an organization to Agile methodologies |