TermDefinition
ProductThe output of the project, it is something of value that has clearly defined stakeholders, users and boundaries
Product GoalThe future state of the Product, illustrating what the long-term goal of the Product is
Product BacklogAn evolving and prioritised list of work items that need to be done on to fulfill the Product Goal
Definition of DoneThe set of standards that the work on a Product Backlog item must meet to be considered complete
Scrum TeamA small team of people working together on building the Product, working towards the Product Goal
Product OwnerThe person accountable for the Product Backlog and ensuring the Product Goal is worked towards
Scrum MasterThe person who acting as the coach for the team helps makes sure everyone is working effectively under Scrum
DevelopersThe people in the Scrum Team completing the work in the Product Backlog
SprintsFixed-length blocks of work done on the Product to complete items from the Product Backlog
Sprint GoalA statement on why the current Sprint is valuable to stakeholders
Sprint BacklogThe selected Product Backlog items for a given Sprint along with the Sprint Goal and the plan for getting the work done within the Sprint
IncrementOne or more “Done” work items that are a usable step towards the Product Goal
Scrum EventsFormal Scrum events that happen during every Sprint
Sprint PlanningThe first Scrum Event where the Scrum Team establishes the Sprint Goal and Sprint Backlog for the current Sprint
Daily ScrumA daily Scrum Event where the developers meet to review progress on the Sprint Goal and adapt the Sprint Backlog if required
Sprint ReviewThe second last Scrum Event where the Scrum Team and the Product stakeholders meet to review Sprint outcomes and the progress towards Product Goal
Sprint RetrospectiveThe last Scrum Event where the Scrum Team meet and review how the Sprint went