Kanban
Scrum
Roles and Responsibilities
Product Backlog
Other
100

When the tech lead meets with the Product Owner prior to understand relative priority, business value and to break epics into user stories

What is Backlog Refinement?

100

The short cycle iterations which result in a complete component or product.

What are Sprints?

100

This person directly interfaces with the business to identify capture business value and build the product roadmap. 

Who is the Product Owner?

100

A brief, simple requirement statement from the perspective of the user

What is a User Story?

100

What tool do we use to manage Agile projects?

What is JIRA?

200

The maximum amount of work that can exist a status

What are Work In Progress Limits?

200

A presentation made by the scrum team to the product owner at the end of each sprint so that the owner can provide feedback about the deliverable and its quality.

What is a Demo Session?

200

Anyone who derives value out of product being developed.

What is a stakeholder?

200

Usually a collection of related user stories for a desired functionality

What is a Feature/Epic?

200

This is where you go to log a help ticket for the JIRA support team

300

The visualization of all the work in progress

What is Work Visualization?

300

Where all scrum team members meet briefly, 15 minutes or less, to explain to the other members what they worked on the previous day, what they're working on today and what impediments they have.

What is a Daily Stand Up meeting?

300

Traditionally, this role is the leader of the software development life cycle, but in Agile Scrum, they step aside and yields to the scrum team and product owner, playing an ancillary role instead.

What is a project manager?

300

Pass all these and the user story is nearly "done"

What is Acceptance Criteria?

300

The focus on adaptability and communication in both development and operation teams to centralize the full scope of work impacting a team and prioritize that work against all existing efforts

What is Agile Operations?

400

Agreements on what is required before a task can move to the next workflow stage

What are Kanban Policies

400

When the scrum team meets and determines what user stories will be developed and discuss any logistical issues that will influence the teams successful delivery of features chosen by the team.

What is Sprint Planning?

400

This role eliminates the team's impediments, monitors burn down, and ensures crystal clear communications are maintained among everyone involved in the project.

What is the Scrum Master?

400

This must be agreed to and met before a story can move to the next stage

What is "the definition of done"?

400

The first release the user can play with

The first release early adopters will want to use, and 

The first release users realize business value from

What are Earliest Testable Products, Earliest Usable Products, and Earliest Lovable Products?

500

The process where new work is continuously prioritized and the DevOps team select the next highest prioritized story to work on

What is Continuous Flow?

500

At the end of each sprint, the scrum team meets to discuss what went well, what did not go well and what should be changed.

What is a Sprint Retrospective?

500

This role understands the value of the project, is available to the scrum team in real time everyday, plans releases and accepts the software.

What is the Product Owner?

500

This acronym guideline should be followed when writing user stories

What is INVEST?

Independent, Negotiable, Valuable, Estimable , Small, Testable

500

This can contains a set of Sprints (Scrum), it includes all CAB activities and they can happen monthly to quarterly (Daily & Weekly are achievable)

What are Release Cycles?

M
e
n
u