Micro-Scrum

Published on Apr 1, 2025, filed under management (feed). (Share this on Mastodon or Bluesky?)

Imagine you worked like this:

1. At the start of the week: Get together with the team to decide what to ship—bring live—at the end of the week. Ideally, everyone contributes, but this is intentionally not a requirement.

2. At the end of the week: Get together and look at what was shipped. Everyone high-fives or, together, lands on one lesson to learn.

Of course, this resembles—for it’s inspired by—Scrum and XP. It reflects some key events and values of agile methodologies, from focusing on continuously shipping value to working as a team to learning together from the results.

This sort of micro-scrum can start out independent or complementary to other processes (unless it duplicates them, as would be the case with a functioning sprint goal, review, and retro process), which makes it easy to test and try.

You can even work like this without a team, when defining and reviewing your increments alone. (I’m working like this in my projects, though I’ve arrived at that mode of working in inspiration by Jake Knapp’s and John Zeratsky’s Make Time, setting highlights for each day as well.)

Is this new? Yes and no—“micro-scrum” is being mentioned here and there; but some of the associated ideas, as with sprints, stand-ups, reviews, and retros seem less micro. But newness is not my point—the point is to share and validate ideas. What do you think? What type of micro-scrum have you observed to work well? (Responses are best served on Mastodon.)