The following terms are often used in product development using the Scrum framework:
Scrum Team – Product Owner, Scrum Master and Development Team
Product Owner – The person responsible for maintaining the Product Backlog by representing the interests of the stakeholders, and ensuring the value of the work the Development Team does.
Scrum Master – The person responsible for the Scrum framework, making sure it is used correctly and maximizing its benefits.
Development Team – A cross-functional group of people responsible for delivering potentially shippable increments of product at the end of every Sprint.
Sprint burn-down chart – Daily progress for a Sprint over the Sprint’s length.
Release burn-down chart – Feature level progress of completed Product Backlog Items in the Product Backlog.
Product Backlog (PBL) list – A prioritized list of high-level requirements.
Sprint Backlog (SBL) list – A prioritized list of tasks to complete during the Sprint.
Sprint – A time period (typically 1–4 weeks) in which development occurs on a set of Product Backlog Items that the team has committed to—commonly referred to as a time-box or iteration
Definition of done (DoD) – The exit-criteria to determine whether a Product Backlog Item is complete. In many cases the DoD requires that all regression tests should be successful. The definition of “done” may vary from one Scrum Team to another, but must be consistent within one team.
Velocity – The total effort a team is capable of in a Sprint. The number is derived by evaluating the work (typically in user story points) completed in the last Sprint. The collection of historical velocity data is a guideline for assisting the team in understanding how much work they can likely achieve in a future Sprint.
Impediment – Anything that prevents a team member from performing work as efficiently as possible.