Glossary - Scrum

B
Burndown Chart: Graphical representation of the remaining work to do for a given period, updated as often as possible.
D
Daily Standup: The time when the team meets to discover impediments, progress and the general state of the Sprint from each other. The daily standup occurs at the same time, same place and is only available for team members to express their status, not interested stakeholders.
I
Impediments: Impediments are any hurdles or problems that the team encounters that hampers their ability to work through their sprint tasks. Impediments are usually removed by the Scrum master.
P
Product Backlog: The Product Backlog is a prioritized list of features that will go into the product. The highest priority items are at the top, and the backlog is maintained by the Product Owner.
Product Backlog Effort: A Product backlog Item has an amount of effort associated with it. This represents a team estimation as to the complexity of the item and is usually expressed in "Ideal Days" or "Story Points".
Product Backlog Item: The Product Backlog contains a list of features also referred to as Product Backlog Items.
Product Owner: The Product Owner is the role in charge of the product that is being built by the team. The Product Owner decides the priority of the Product Backlog, and also when the product should be released.
R
Release: Usually, the term "Release" defines the period of time from the start of a version development to its release, going through a series of successive sprints.
S
ScrumMaster: The ScrumMaster is the person who ensures that the process is followed by all roles. This role is a facilitator, coach, mentor for the roles involved in the process.
Sprint: A sprint is a Timebox leading to create a product increment. It's the Scrum term for "iteration".
Sprint Backlog: The Sprint Backlog contains the work that the team has committed to for the Sprint, including all of the tasks that need to be completed to implement the Product Backlog Items. The Sprint backlog is owned by the team.
Sprint Burndown Chart: The Sprint Burndown Chart is a graphical representation of the work remaining over the duration of the Sprint. The Vertical axis displays the hours of effort remaining for the Sprint. The horizontal axis displays the days of the Sprint. The burndown is supposed to be shown by the line of descent from the start of the Sprint with the starting hours, down to the end of the Sprint with no hours remaining. The Burndown chart is used by the team to gauge how well the Sprint is going.
Sprint Goals: The Product Owner and Team will identify some scope for the Sprint to provide some indications of the expectations for the Sprint and provide some measure of success. Sprint goals help provide focus on Team design and implementation decisions.
Sprint Planning Meeting: The start of a Sprint is marked by a planning meeting where the Product Owner will go through the highest priority Product Backlog items, and based on that information the team will select the Product Backlog Items they will be implementing during the next Sprint.
Sprint Retrospective Meeting: At the end of the Sprint the Team will meet at a retrospective to discuss the things that worked and did not work during the Sprint. This provides the feedback and adapt opportunity for the process and allows the process to evolve and fit the team.
Sprint Review Meeting: At the end of the Sprint, the Team will show the progress made during the Sprint to the Product owner and key stakeholders. Only Product Backlog Items that were completely done are shown at the review meeting.
Sprint Task: The Sprint Backlog is made up of a list of tasks that the team needs to work through to complete the Product Backlog Items that they committed to at the start of the Sprint. The Sprint tasks have attributes to show the point person, the state of the task (i.e. not started, in progress, impeded or done) and the amount of time left to complete the task.

Sprint tasks are the smallest level of work represented in either of the backlogs and refer to work that is usually up to 16 hours of work.
Story Point: Story points are a measurement employed to indicate the effort required to implement a user story, or product backlog feature.
T
Team: The Team is a cross-functional group of 5-9 people who commit to delivering high value increments of product functionality to the customers each Sprint. The Team is in charge of their own destiny since they are empowered to organize themselves to make sure that all of the work is completed.
Theme: A theme defines a functional group of requirements.
Timebox: A period of time with a fixed and unmovable end date even if all objectives aren't reached.
V
Velocity: Velocity is a metric that shows the rate of delivery for a team. A teams velocity shows how many story points they are able to convert into increments of potentially shippable product each sprint.