T-shirt Sizing
An estimation method where stories get sized as XS/S/M/L/XL instead of numeric points — rougher, faster, no false precision.
Example:'That's obviously an M, let's not spend ten minutes debating 5 vs 8 points on it.'
CollectionsField terms59
The vocabulary around daily standups and the agile ceremonies, roles, and artifacts that surround them.
For anyone joining an agile team: engineers, PMs, designers.
Lobyas brings these back across Read, Review and Quiz until they stick.
Sign-up is by invite. Request access, or sign up with an invite code if you have one.
An estimation method where stories get sized as XS/S/M/L/XL instead of numeric points — rougher, faster, no false precision.
Example:'That's obviously an M, let's not spend ten minutes debating 5 vs 8 points on it.'
A concrete, assigned change agreed on in retro — not just a complaint, an actual thing someone owns doing.
A separate, smaller conversation spun out of something raised in standup that needed more than a sentence.
Example:'Let's take that in a follow-up after standup' — the standard way of moving a rabbit hole out of the main meeting.
Rotating who facilitates standup each day or week, instead of always having the Scrum Master run it.
Free to start: you get AI credits when you join and a refill every month. Read, Review and simple quizzes never use credits, and there are no due dates to fall behind on.
Sign-up is by invite. Request access, or sign up with an invite code if you have one.
Generic term for any short meeting whose purpose is just getting everyone on the same page — standup is one specific kind of sync.
Anyone outside the immediate team with an interest in what's being built — a client, an exec, another team depending on the output.
Example:Marketing is a stakeholder for a feature launch even though they're not writing any code.
The person who owns the product backlog and decides what gets prioritized and why, based on what's valuable to users and the business.
The person responsible for running the ceremonies, clearing impediments, and protecting the team from process nonsense — not a manager, not a project lead.
A small, semi-autonomous cross-functional team, popularized by Spotify's org model — same idea as a scrum team, different label.
A team with all the skills it needs to ship something end-to-end, without depending on another team for every piece.
Example:One squad with a designer, two engineers, and a QA person, instead of routing every task through three separate specialist teams.
Scrum's term for any of the recurring scheduled meetings — planning, standup, review, retro.
The regular rhythm of a team's meetings and cycles — daily standup, weekly planning, biweekly retro.
Shortcuts taken to ship faster now that cost extra work to clean up later.
Example:Hardcoding a config value to hit a deadline instead of building the proper settings page.
A cap on how many items can sit in a given column (like 'In Progress') at once, forcing the team to finish things before starting new ones.
Example:WIP limit of 3 on 'In Progress' means a 4th ticket can't move there until something else moves out.
The specific, testable conditions a story has to meet to be considered complete.
Example:'User sees an error message if password is under 8 characters' — specific and checkable, unlike 'password validation works.'
The checklist a ticket has to pass before it's allowed into a sprint — clear acceptance criteria, no open questions, properly sized.
The team's agreed checklist for when a piece of work actually counts as finished — not just coded, but tested, reviewed, deployed, whatever the team decided.
Example:DoD might include: code reviewed, tests passing, deployed to staging, QA signed off.
Work quietly getting added to a sprint after it's already started, without anyone officially replanning.
Example:Sprint starts with 10 tickets; by day 3 there are 14 because stakeholders kept asking for 'just one more small thing.'
Like a burndown chart but tracking completed work trending up — and it also shows if scope itself increased mid-sprint.
A chart showing remaining work in the sprint over time — ideally trending down to zero by the last day.
Showing the newest 20 of 59 terms. Add the collection to Lobyas to study all of them.