User story: A short description of desired functionality (user requirement).
Story point: Measure of effort required for implementing a user story. Usually corresponds to an ideal day of work.
Product Backlog: A set of all user stories currently known. Sprint An iteration.
Sprint Backlog is subset of the Product Backlog consisting of user stories that the Team committed to implement in a particular Sprint. Each story is further split into tasks.
Scrum Team developers responsible for implementing functionality.
Product Owner represents the interests of everyone with a stake in the project and maintains the Product Backlog.
ScrumMaster manages the Scrum process and ensures that everyone follows Scrum rules and practices.
Velocity represents the amount of work accomplished in each Sprint expressed in story points. It is typically used to compare planned vs actual velocities
Burndown chart shows the amount of work remaining by plotting the sum of story points of all unfinished stories in the Product Backlog.
Release burndown chart tracks story points across sprints, Sprint burndown chart tracks story points within a sprint
Sprint planning happens at the beginning of each sprint to plan the work to be performed in the Sprint.
Sprint review is held at the end of the Sprint to gauge what has been built and adapt the Product Backlog if needed
Sprint Retrospective is held after Sprint review to gauge how to inspect itself and create a plan for improvements to be enacted during the next Sprint. Usually shorter than Sprint Review and under 3 hours.