227- Development Team Roles

Vocabulary flashcards covering essential roles, artifacts, and ceremonies in Agile project management.

Development Team (Delivery Team)

The self-organizing group that builds and tests product increments, updates information radiators, writes acceptance tests, demos work, and performs sprint/release planning and estimation.

Product Owner (Customer)

The role responsible for prioritizing features, managing and grooming the product backlog, defining acceptance criteria, setting release dates, and participating in planning, reviews, and retrospectives.

Scrum Master / Agile Project Manager / Coach

A servant leader who facilitates meetings, mentors the team, ensures visibility of plans and progress, collaborates with the product owner, and removes impediments.

Self-Organizing Team

A team that directs its own work, deciding how tasks are accomplished without external command-and-control.

Information Radiator

Any visible display (e.g., whiteboard, Kanban board, task board) that shows up-to-date project information to stakeholders.

Daily Stand-Up

A brief daily meeting where team members share progress, plans, and impediments.

Sprint Review

A session at the end of a sprint where the team demos the completed product increment to stakeholders for feedback.

Retrospective

A meeting held after each sprint where the team reflects on its process and identifies improvements.

Sprint Planning

A meeting where the team and product owner decide which backlog items will be worked on in the upcoming sprint and estimate the effort.

Release Planning

High-level planning that outlines which features will be delivered in upcoming releases and their targeted dates.

Product Backlog

An ordered list of all desired product features, maintained and prioritized by the product owner.

Backlog Grooming (Refinement)

The ongoing activity of updating, clarifying, and reprioritizing items in the product backlog.

Acceptance Criteria

The conditions that a product backlog item must meet for the product owner to accept it as complete.

Acceptance Test

The test written by the development team to verify that a backlog item meets its acceptance criteria.

Servant Leader

A leadership style where the leader’s primary goal is to support the team, enabling autonomy, growth, and obstacle removal.

Estimation

The process by which the development team forecasts the effort or time required to complete backlog items.

Liaison

The role of the scrum master in communicating progress and issues between the development team and stakeholders.

Kanban Board / Task Board

A visual tool used to track work items as they move through stages of completion.