LIST OF VOCABULARY WORDS

• Acceptance Criteria: Conditions that a product must satisfy to be accepted by a user or customer.
• Agile: A methodology that promotes continuous iteration of development and testing throughout the software development lifecycle.
• Backlog: A list of tasks or features prioritized by importance and to be addressed by the development team.
• Burn-Down Chart: A visual representation of work left to do versus time.
• Burn-Up Chart: A chart that shows work completed against a total scope.
• Cross-Functional Team: A team composed of members with various functional expertise working towards a common goal.
• Daily Scrum: A short meeting held daily for the development team to synchronize activities and plan for the next 24 hours.
• Definition of Done: A clear and concise list of requirements that software must adhere to for it to be considered complete.
• Definition of Ready: A checklist that ensures user stories are ready to be worked on.
• Development Team: A group of professionals responsible for delivering a potentially releasable increment of the product.
• Epic: A large body of work that can be broken down into smaller tasks or user stories.
• Feature: A distinct aspect of a product, such as a function or characteristic.
• Increment: The sum of all the product backlog items completed during a sprint, along with the increments of all previous sprints.
• Iteration: A time-boxed period during which development occurs.
• Kanban: A visual process-management method that tells what to produce, when to produce it, and how much to produce.
• Lean: A methodology focused on minimizing waste within manufacturing systems while simultaneously maximizing productivity.
• Planning Poker: A consensus-based technique for estimating, mostly used to estimate effort or relative size of development goals.
• Product Backlog: An ordered list of everything that might be needed in the product.
• Product Backlog Refinement: The act of adding detail, estimates, and order to items in the product backlog.
• Product Owner: The person responsible for maximizing the value of the product and the work of the development team.
• Release Planning: The process of planning the features and timeline for the release of a product.
• Retrospective: A meeting held at the end of an iteration in which the team discusses what went well and what could be improved.
• Scrum: An Agile framework for managing knowledge work, with an emphasis on software development.
• Scrum Master: A facilitator for the team and the product owner, ensuring that the Scrum process is followed.
• Scrum Team: A self-organizing team consisting of a Scrum Master, Product Owner, and development team.
• Scrumban: A hybrid methodology that combines Scrum and Kanban.
• Sprint: A time-boxed period, usually 1-4 weeks, during which a specific set of work must be completed and made ready for review.
• Sprint Backlog: A list of the work to be performed during the sprint, typically derived from the product backlog.
• Sprint Goal: A short, concise statement of what the team plans to achieve during the sprint.
• Sprint Planning: A meeting where the team selects a set of product backlog items to work on during a sprint.
• Sprint Retrospective: A meeting where the team looks back on the sprint to discuss what went well and what needs improvement.
• Sprint Review: A meeting where the team demonstrates what they accomplished during the sprint.
• Stakeholder: Anyone with an interest in the outcome of a project, such as customers, users, or sponsors.
• Story Point: A unit of measure used in Agile to estimate the effort required to implement a story.
• Task: A piece of work assigned to a person or team to accomplish a goal.
• Test-Driven Development (TDD): A software development process that relies on the repetition of a very short development cycle.
• User Story: A simple description of a feature written from the perspective of the person who desires the new capability.
• Velocity: A measure of the amount of work a team can tackle during a single sprint.
• WIP (Work in Progress) Limit: A strategy for preventing bottlenecks in a process by limiting the amount of work in progress.
• Agile Manifesto: A formal proclamation of four key values and 12 principles to guide an iterative and people-centric approach to software development.
• Iteration Review: A meeting to inspect the increment and adapt the product backlog if needed.
• Refactoring: The process of restructuring existing computer code without changing its external behavior.
• Scrum of Scrums: A technique to scale Scrum up to large groups (over a dozen people), consisting of dividing the groups into smaller teams of 5-10.
• Servant Leader: A leadership philosophy in which the main goal of the leader is to serve.
• Sprint Zero: An initial sprint used for planning and setting up the infrastructure and environment needed for development.
• Time-Boxing: Allocating a fixed, maximum unit of time for an activity.
• Wireframe: A visual guide that represents the skeletal framework of a website or application.
• XP (Extreme Programming): A software development methodology aimed at improving software quality and responsiveness to changing customer requirements.