Agile Principles
Agile Roles
Scrum Process
Agile Terminology
Agile Ceremonies
100

This principle describes engagement visibility and establishes trust across all internal and external participants.

What is Transparency?

100

Folks who estimate the effort, develop and test software, and identify impediments.

What is the Scrum Team?

100

This usually lasts between 2-4 weeks.

What is a Sprint?

100

The format is as follows: Who, What, Why or Gain and Understanding

User Story

100

Each day, 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.

Daily Stand-Up

200

A scrum team is known as this if they have a high degree of autonomy and are responsible for the management of their own work.

What is "Self Organizing"?

200

Anyone who derives value out of deliverable(s) in the current cycle but are not part of the Scrum Team.

What is a Stakeholder?

200

The prioritized list of user stories the Scrum Team commits to working on during a specific iteration.

What is a Sprint Backlog?

200

Used to build out the Story map, this is the high-level component, or defined area, of the audit.

Epic

200

At the beginning of each sprint, 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.

Sprint Planning

300

This agile principle allows for prioritization of risk and drives business value.

What is "flexible Scope"?

300

This role has primary responsibility to continually help the team to grow in their agile adoption and practices.    They may also schedule and facilitate sprint ceremonies for the team.

What is a Scrum Master?

300

The process of ranking the user stories in the audit backlog.

User Story Prioritization

300

In the beginning of a project the Product Owner is responsible for completing this. The Scrum Team should refer back to this often for reinforcement.

Audit Canvas

300

This is done once per sprint, where the Scrum Team, Scrum Master, and Product Owner update user stories, refine acceptance criteria, and review user stories for long range sprint planning.

Backlog Refinement

400

When a user story has been completed to the satisfaction of the Product Owner and meets the objective of the audit with data driven results.

What is "Definition of Done (DoD)"?

400

This highlights the associated risks and requirements to complete a specific user story.

Acceptance Criteria

400

This details the project scope and bridges the audit canvas to the user story document.

Story Map

400

These occur one time per sprint and bring together Subject Matter Experts to engage in an open feedback environment.

Sprint Checkpoint

500

Agile was born to provide an alternative to this project management approach.

What is Waterfall?

500

This role understands the value of the deliverables, helps to eliminate team impediments and is available to the scrum team in real time everyday.

What is a Product Owner (Or Squad Lead)?

500

Throughout the sprint the scrum team produces these with help from product owner and stakeholders and testing.

Point of View (POV)

500

This is used to visualize the progress of the audit team and facilitates transparency to the stakeholders regarding emerging Point of Views.

Hypothesis Board

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.

Sprint Retrospective