Agile: A set of principles for software development that emphasizes flexibility, collaboration, and customer satisfaction.

Scrum: A framework within Agile for developing, delivering, and sustaining complex products.

Sprint: A set time period during which specific work has to be completed and made ready for review.

Kanban: A lean method to manage and improve work across human systems.

Product Owner: The role in Scrum responsible for defining the features of the product and deciding on release date and content.

Scrum Master: The facilitator for an Agile development team; responsible for managing the exchange of information between team members.

User Stories: Short, simple descriptions of a feature told from the perspective of the user who desires the new capability.

Backlog: A list of tasks or goals that a team maintains or accomplishes.

Stand-up Meeting: A daily team meeting held to provide a status update to the team members.

Iteration: A time-boxed period of development where a team works to complete a specific goal.

Agile Coaching: The practice of helping organizations implement Agile methodologies in their workflows.

Retrospective: A meeting held at the end of an iteration in which the team reflects on that iteration and identifies improvements for the next one.

Burn-down Chart: A graphical representation of work left to do versus time.

Continuous Integration: The practice of merging all developer working copies to a shared mainline several times a day.

TDD (Test-Driven Development): A software development process that relies on the repetition of a very short development cycle.

Pair Programming: A practice in which two programmers work together at one workstation.

Agile Project Management: An iterative approach to managing software development projects that focuses on continuous releases and incorporating customer feedback with every iteration.

Velocity: The amount of work a team can complete in a single sprint.

Epic: A large body of work that can be broken down into smaller tasks (stories).

Story Points: A unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product backlog item or any other piece of work.

Refactoring: The process of restructuring existing computer code without changing its external behavior.

Lean Software Development: An adaptation of Lean manufacturing principles and practices to the software development domain.

Spike: A product-testing method that uses the simplest possible program to explore potential solutions.

Minimum Viable Product (MVP): A product with just enough features to satisfy early customers and provide feedback for future development.

Definition of Done (DoD): A clear and concise list of criteria which must be met before a product increment is considered complete.

Release Planning: The process of planning the delivery of a set of functionalities and product increments.

Daily Scrum: A daily time-boxed event of 15 minutes for the Development Team to synchronize activities and create a plan for the next 24 hours.

Sprint Review: A meeting at the end of each sprint to inspect the increment and adapt the Product Backlog if needed.

Sprint Retrospective: A meeting at the end of the sprint where the team discusses the just-concluded sprint and determines what could be changed that might make the next sprint more productive.

Agile Manifesto: A formal proclamation of four key values and twelve principles to guide an iterative and people-centric approach to software development.