The following terms are often used in a scrum process. Since, these are universal terms and definitions, they have been picked up from wiki.
- Scrum Team – It comprises of 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 process, 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 backlog items that the team has committed to—commonly referred to as a time-box or iteration.
- Spike – A time boxed period used to research a concept or create a simple prototype. Spikes can either be planned to take place in between sprints or, for larger teams, a spike might be accepted as one of many sprint delivery objectives. Spikes are often introduced before the delivery of large or complex product backlog items in order to secure budget, expand knowledge, or produce a proof of concept. The duration and objective(s) of a spike is agreed between product owner and development team before the start. Unlike sprint commitments, spikes may or may not deliver tangible, shippable, valuable functionality. For example, the objective of a spike might be to successfully reach a decision on a course of action. The spike is over when the time is up, not necessarily when the objective has been delivered.
- Tracer bullet – The tracer bullet is a spike with the current architecture, current technology set, current set of best practices that results in production quality code. It might just be a very narrow implementation of the functionality but is not throw away code. It is of production quality, and the rest of the iterations can build on this code. The name has military origins as ammunition that makes the path of the bullet visible, allowing for corrections. Often these implementations are a ‘quick shot’ through all layers of an application, such as connecting a single form’s input field to the back-end, to prove the layers connect as expected.
- Tasks – Work items added to the sprint backlog at the beginning of a sprint and broken down into hours. Each task should not exceed 12 hours (or two days), but it’s common for teams to insist that a task take no more than a day to finish.
- 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 from the last sprint’s backlog items. The collection of historical velocity data is a guideline for assisting the team in understanding how much work they can do in a future sprint.
- Impediment – Anything that prevents a team member from performing work as efficiently as possible.
- Sashimi – A term used to describe one or more user stories, indicating that they are thin slices of a product feature or capability.
- Abnormal termination – The product owner can cancel a sprint if necessary. The product owner may do so with input from the team, scrum master or management. For instance, management may wish to cancel a sprint if external circumstances negate the value of the sprint goal. If a sprint is abnormally terminated, the next step is to conduct a new sprint planning, where the reason for the termination is reviewed.
- ScrumBut – ScrumBut (or Scrum but) is a term to describe the approach of a team who have adapted the scrum process to their own needs in some way contradictory to supposed pure scrum.