SCRUM Vocabulary

Daily Scrum

A 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. Questions that should be asked: What have you done? What are you going to do? What are the impediments of risks?

Sprint Review

A demonstration meeting of the work that is done. Includes product owner and clients.

Working Agreement

A formal agreement between team members to perform activities or to abide by certain guidelines.

Product Backlog

A list of all things that needs to be done within the project. Product owner is responsible for the product backlog.

Sprint Backlog

A list of tasks identified by the Scrum team to be completed during the Scrum sprint. Taken off of the product backlog. The team is responsible for creating the Sprint Backlog.

Sprint Retrospective

A meeting of the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

Product Owner

A member of the agile team responsible for defining stories and prioritizing the team backlog. Also has the vision for the product.

Development Team

A self-organizing (choosing the jobs that they want to accomplish), cross-functional team of people who collectively are responsible for all of the work necessary to produce working products

Sprint

A time period of one month or less when a part of the project is developed.

Time-boxed

A timebox is a previously agreed period of time during which a person or a team work steadily towards completion of some goal.

Definition of Done

An acceptance criteria that drives the quality of work and is used to assess when a User Story has been completed. Should be created when creating sprint backlog.

Triple Constraint

Combination of the three most significant restrictions on any project: scope, time, and cost. If you shift one of these constraints, the quality is going to shift.

Scrum Master

Facilitator for a development team, keeps the noise (distractions) away, makes sure team is focused, provide resources to the team.

Agile Manifesto

Formal proclamation of four key values and 12 principles to guide an iterative and people-centric approach to software development.

Acceptance Criteria

Performance requirements and essential conditions which must be met, required for a user story to be considered complete

Product Increment

What is delivered at the end of the Sprint.