Ready-set-Sprint
Product Ops
Minimum Viable Product Mang.
(MVPM)
Agile-phabet Soup
Name that Product/Project
100

Visualize the race ahead. This practice lets teams manage progress by moving tasks across a board from "To Do" to "Done" during a sprint

Kanban

100

The name of the meeting where engineers and product managers sync up to align on initial project goals and planning

Builder Huddle

100

The term that describes a concise description of a feature or requirement from an end user’s perspective.

User Story

100

Daily "soup of the day" meeting ensures everyone knows the ingredients (tasks) required to deliver the final dish (sprint goal).

Standups

100

πŸ˜οΈπŸ›£οΈ

Living Streets

200

Get ready to line up! This "waiting room" is filled with well-scoped issues and stories, each poised to join the starting lineup for the next sprint.

Backlog

200

The process to assign value and effort scores for projects.

Evaluations

200

The name given to a large body of work that is broken down into smaller tasks which often represents a major them or initiative.

Epic

200

This kind of "recipe book" provides the strategic direction and steps needed to cook up new features over multiple releases.

Roadmaps

200

πŸ“ŠπŸ”πŸš¦

Data Tracker

300

On your mark, get set! This is the standard length of a sprint cycle, giving teams an amount of time to dash toward the finish line

Two weeks

300

The meeting held at the start of a new project to establish objective, team roles, and initial planning.

Kick off meeting

300

This type of change involves improving an existing feature to address usability, performance, or quality without significantly altering its core functionality.

Enhancement

300

The "soup tasting" meeting do teams reflect on their previous efforts to refine the recipe for future sprints.

Retrospectives

300

πŸ’¨πŸƒβ€β™‚οΈ

Dash

400

This "finish line celebration" that marks the successful completion of a project, when the team launches their work to the world and celebrates with a party.

Release

400

The label that’s used to show projects on the DTS website.

Project Index

400

Term used to describe a new functionality to a product that delivers value to users and is often planned, designed, and implemented as part of a larger road map.

Feature

400

The "soup kitchen" meeting do teams carefully select ingredients (user stories) to ensure the final dish (sprint) is ready on time and satisfies customer taste buds.

Sprint Planning

400

πŸ›΅

Moped

500

Take a victory lap. This event happens after a sprint, where the team presents their recent accomplishments and reflects on their progress with stakeholders.

Sprint Review

500

The process of defining and narrowing down project objectives and deliverables to set clear boundaries and expectations

Scoping

500

Metric used in Agile to estimate the relative effort required to implement a user story or feature - size or estimate.

Story Points

500

This "soup tasting" session allows teams to refine the list of ingredients (backlog items) to ensure the best flavors (user stories) are prioritized for the next sprint.

Backlog Refinement

500

πŸ§‘πŸš§

Amanda

M
e
n
u