Scrum Roles
Agile
Meetings and Ceremonies
Terminology
100

This person facilitates team decisions and ensures impediments are removed.

Scrum Master

100

This high speed event usually lasts between 2-4 weeks.

Sprint

100

This meeting is Torrent specific and is put in place to review the items being delivered to production and align on status of our process

Sprint Release Planning

100

Texas Hold'em is a close cousin of this estimation tool.

Planning Poker

200

This is usually 5-9 people in size.

Delivery Team

200

What document includes the following information: Deploy to all applicable environments (i.e., team branch, dev, stage, production) is green (successful) in Azure DevOps 

Definition of Done

200

As the product owner, your responsibility is to make sure the product backlog is well groomed, its items are prioritized, and its high-priority items detailed - prior to this meeting

Sprint Planning

200

The format is as follows: As a, I want to, so that.

User Story

300

The one and only person responsible for the managing the product backlog and ensuring the value of the work performed.

Product Owner

300

This is the ongoing effort to improve products, services, or processes.

Continuous improvement 

300

Is a great opportunity to understand the progress being made and to see if the team needs help.

Scrum or Standup

300

DAILY DOUBLE: What does ACOP stand for?

Agile Community of Practice

400

The product owner is supported by these additional roles by jointly grooming the product backlog.

Scrum master, development team members

400

Waterafll projects have fixed requirements and usually negotiate Cost and Schedule. Agile projects negotiate this.

Scope

400

A ceremony scrum teams use to inspect, reflect, and adapt at the end of every development cycle

Retrospective

400

A priortized list of the outstanding work necessary to bring the product to life.

Product backlog

500

These people are apart of the team and project but don't have current contributions to the project. Hint: they go bock bock. 

Chickens 

500

The prioritized list of user stories the delivery team commits to working on during a 2-4 week development cycle.

Sprint Backlog

500

This term characterizes the meeting that addresses the backlog needing regular attention and care, it needs to be carefully managed.

Refinement/Grooming

500

The number of story points that the team can complete in a given sprint

Velocity 

M
e
n
u