Project Management Glossary

Ceremonies: These are the events that the scrum team participates in for a sprint. It allows the team to have transparent clear communicatation, adapt and continuously learn. The key ceremonies are Sprint Planning, Daily Scrum or Standup, Sprint Reviews and Sprint Retrospectives.
Epic: A large body of work consisting of multiple user stories.
Impediments Backlog: A list of impediments that need to be addressed by the Scrum Master for the team to carry on working.
Kanban: A signboard used as a visual tool to control production.
MVP: A Minimum Viable Product has just enough features to satisfy early customers and provide feedback for future product development.
Product Backlog: A list of all work items for a given product which can include requirements, features (stories), technical tasks, spikes and fixes. Every week, the team looks at this list to decide which of these they should work on in the next sprint.
Release Burn-up: A graphical chart used to show progress at a release level and to predict when a release will be finished using Sprint Velocity.
Spike: A special type of task which needs to be researched, prototyped or architected before it is clear how user story implementation can proceed.
Sprint: In scrum, the work is divided into short time-boxed iterations called sprints that are usually 1 to 3 weeks.
Sprint Backlog: A log of work items to be completed in each sprint.
Sprint Board: A table that tracks the progress of the work committed for the sprint.
Sprint Burndown: A graphical representation of the work completed and remaining measured in story points over the length of the sprint.
Sprint Retrospective: The last step of every sprint is a Retrospective. This allows the team to talk about and document what worked well and what didn’t. It can be about the sprint, the project, the people, relationships, tools and even ceremonies. Its not about what went wrong but more about what went well and what can be improved in the future.
Sprint Review: Allows the team to provide a demo of the sprint so that all team members understand what was accomplished from the backlog. It also allows the product owner to re-work the backlog based on the current sprint to serve as the starting point for the next sprint planning.
Sprint Velocity: The number of story points that a scrum team completes in a sprint.
User story: Description of a software feature from an end-user perspective. This is the most widely accepted method of identifying and understanding user requirements. See https://www.atlassian.com/agile/project-management/user-stories for more details.