---
title: The Sprint and Its Events
generated: true
---

<!-- Generated from docs/glossary.yml by tools/build-public-docs.mjs. Do not edit; edit the term. -->

# The Sprint and Its Events

6 words that belong together: Sprint, Sprint Planning, Backlog Refinement, Sprint Review, Retrospective, Rollover.

## Sprint

**Plain word:** A fixed stretch of work, one month or less.

A set length of time in which the team builds what it chose at the start, then shows it and looks back.

### In Pulse, the house method

Pulse runs inside the sprint, and nothing waits for its end. The calendar says what falls due on each day, each meeting is prepared before its day, and the agents keep the work moving between meetings while people decide.

### How most teams run it

- A sprint is a fixed stretch of time, one month or less, in which the team builds what it chose at the start.
- It opens with Sprint Planning and closes with the Sprint Review and then the Retrospective.
- Its length stays the same from sprint to sprint, so the team learns how much fits in one.

**How long:** one month or less, and the same length each time; one or two weeks is common. **It starts from:** an ordered Product Backlog; the team's choice of what to build, made at Sprint Planning. **It produces:** a working increment the team can show; what was not finished, to be rolled over.

### What StellarView does for it

- The Conductor starts the sprint in Jira when it launches an epic, and keeps the sprint's name, board, dates and issue count on the run.
- The Galaxy board shows the sprint as days across, with what fell due on each day and how long it has waited.
- A sprint that has ended stays on the board, hatched day by day, until it is closed.

### Why it matters

A fixed length gives the team a steady beat: a plan at the start, a showing at the end, and a look back before the next one.

**If it is skipped:** Without an end date the work runs on with no point at which anyone checks it against what was asked.

Related: [Live meeting](/glossary#live-meeting).

[In the glossary](/glossary#sprint).

## Sprint Planning

**Plain word:** Choosing what the sprint will build.

The meeting that opens a sprint, where the team agrees its goal and picks the work that serves it.

Also written: Planning.

### In Pulse, the house method

In Pulse, planning starts prepared. Each epic comes filled from the Big Bang, with its gaps answered and a person accountable, so the meeting is spent deciding, not discovering. For new work, the Conductor's POC station can build a working preview first.

### How most teams run it

- The team agrees why this sprint is worth doing: its goal.
- It picks the items from the top of the Product Backlog that serve that goal and fit in the sprint.
- It says how it will build them, enough to start.

**How long:** up to two hours for a one-week sprint (the Scrum Guide's eight hours for a month, scaled down). **It starts from:** an ordered Product Backlog; what the team finished in the sprints before, as a guide to how much fits. **It produces:** the sprint goal; the Sprint Backlog: the items chosen, and a plan to start them.

### What StellarView does for it

- Planning is a meeting on the team file, held as a batch or live meeting with the team's seats.
- The Planning room shows the sprint, its epics by phase, the hours behind each, and the questions the plan could not answer.
- The Conductor has a planning station for each epic. It prepares the meeting and waits for a person's click.

### Why it matters

It is the one moment the whole team agrees what the sprint is for, so every later choice can be checked against that.

**If it is skipped:** The sprint has no goal, so at the review there is nothing to measure what was built against.

[In the glossary](/glossary#sprint-planning).

## Backlog Refinement

**Plain word:** Getting the next work ready.

The ongoing work of making the next backlog items ready. Many teams give it a meeting in the middle of the sprint.

Also written: Grooming.

### In Pulse, the house method

In Pulse, refinement does not wait for the meeting. The Big Bang fills each epic with its requirements, phases, work units and the gaps still open, so the meeting works only on what is unclear.

### How most teams run it

- It is ongoing work, not one of Scrum's events: the team keeps looking at the items coming up next in the Product Backlog. Many teams set aside a meeting for it.
- It splits the large ones, makes each one clear enough to build, and sizes it.
- The Product Owner puts them in order, so the next Sprint Planning starts from items that are ready.

**How long:** no set length: the Scrum Guide calls it an ongoing activity. Many teams hold it as an hour in the middle of a one-week sprint. **It starts from:** the Product Backlog as it stands; what was learned in the sprint so far. **It produces:** the next items, split, clear and sized; the Product Backlog in order.

### What StellarView does for it

- Backlog Refinement is a meeting on the team file. The team file names its seats and what each one speaks to.
- The Backlog room shows what each product has waiting, in an order a person sets, and what each epic has been filled with.
- This is not the Refinement that rewrites a section by chat. That one edits a document; this one readies the backlog.

### Why it matters

Planning goes quickly when the items at the top are already clear and sized.

**If it is skipped:** Sprint Planning spends its time working out what the items mean, and the sprint starts on work that is not ready.

[In the glossary](/glossary#backlog-refinement).

## Sprint Review

*The rudiment for this is recorded and not yet published.*

**Plain word:** Showing what was built.

The meeting at the end of a sprint where the team shows its work running. In this house, the accountable person then accepts it or not.

Also written: Review.

### In Pulse, the house method

In Pulse, the review is prepared ahead. Sue writes the pre-read from the record, each seat comes with its point and its evidence, such as the demo, the commission checks and the test results, and the decision waits for the accountable person.

### How most teams run it

- The team shows what it built this sprint, working, to the people it is for.
- Together they look at what was done against the sprint's goal, and at what is not finished.
- They agree what to do next, and the Product Backlog changes to match.
- In Scrum the review is a working session, not a gate. This house adds one decision after it: the accountable person accepts the work, or not.

**How long:** up to an hour for a one-week sprint (the Scrum Guide's four hours for a month, scaled down). **It starts from:** the working increment; the sprint's goal and its backlog; the pre-read, sent ahead. **It produces:** what is accepted and what is not; changes to the Product Backlog; what the Retrospective should look at.

### What StellarView does for it

- The review is a meeting on the team file. Its brief says what the meeting is for and who it is for.
- Sue, the coordinator seat, writes the pre-read from the engagement's own records. Every point cites a record, or it is struck.
- In the meeting each seat gives one point from the record, and the minutes keep its proposals. Held live, its proposals also go to the ledger, and the Action Center lists them for a person to decide.
- The Conductor's review station prepares the meeting and waits for a person's click. QA Validation and Review and unleash hold the work to look at.

### Why it matters

It is where the people the work is for see it working, and where the plan meets the result.

**If it is skipped:** Work is called done that nobody it was for has seen, and the next sprint is planned without knowing what landed.

[In the glossary](/glossary#sprint-review).

## Retrospective

**Plain word:** Looking back at how the team worked.

The meeting after the review where the team picks a few changes to try next sprint, each with an owner.

Also written: Retro.

### In Pulse, the house method

In Pulse, the look back starts from measurements, not memories. The Spectrograph and the test runs say where the time and money went and what passed, so the team spends its time choosing what to change.

### How most teams run it

- After the review, the team looks at how it worked this sprint: its people, its tools, its way of working.
- It names what went well and what got in the way, with examples.
- It picks a small number of changes to try in the next sprint, each with someone to carry it.

**How long:** up to about forty five minutes for a one-week sprint (the Scrum Guide's three hours for a month, scaled down). **It starts from:** what happened this sprint; what the review raised; the changes picked last time, and whether they held. **It produces:** a short list of changes to try next sprint, each with an owner.

### What StellarView does for it

- The Retrospective is a meeting on the team file, held after the review on the sprint's last day.
- Held live, its proposals land in Follow-ups for the engagement and in the Action Center. Held as a batch meeting, they stay in its minutes.
- The Spectrograph and the test runs give it measured facts about the sprint: where time and money went, and which runs passed.

### Why it matters

It is how the team gets better at the work itself, a little each sprint.

**If it is skipped:** The same problems come back sprint after sprint, because nobody stopped to name them.

[In the glossary](/glossary#retrospective).

## Rollover

**Plain word:** What happens to unfinished work.

The choice, when a sprint closes, of where each unfinished item goes next: the next sprint, the backlog, or split.

### In Pulse, the house method

In Pulse, nothing is left to slide. The board shows each day the sprint runs late, and the close waits as a choice for a named person, with what each way of rolling over does in Jira.

### How most teams run it

- When a sprint closes, some items are not finished.
- In Scrum they go back to the Product Backlog, and the Product Owner orders them again before the next Sprint Planning.
- Many teams instead move them into the next sprint, choose item by item, or split each one into the finished part and what remains.

**How long:** a few minutes, after the Retrospective. **It starts from:** the sprint's unfinished items; what the review and the retrospective decided. **It produces:** each unfinished item placed: the next sprint, the backlog, or split; the sprint closed.

### What StellarView does for it

- The Galaxy board lists six ways to close and roll over, each with what it does in Jira.
- Choosing one on the board does not yet change Jira: the board is a proof of concept and saves nothing.

### Why it matters

It decides on purpose what happens to the work that did not fit, so it neither vanishes nor slides along unseen.

**If it is skipped:** Unfinished items sit in a closed sprint, or slip into the next one without anyone choosing them.

[In the glossary](/glossary#rollover).

