Sprint Review

The Sprint Review screen

NeedsView view

Open the project and click Sprint Review. The page title is the project key followed by Sprint Review. Everyone who can see the project can read the whole screen, guests included.

The screen follows one session. A canceled review never appears. If a review is open, the screen shows it. If none is open, the screen shows the last review in the project's list.

When the project holds two or more reviews, a line of links under the title names each one: Sprint 3, Sprint 4 and so on. The links run in order of the scheduled start of each review. A review with no scheduled start comes last, whatever its dates. Click one to switch. The address then names the session you chose.

A band under the title reads Sprint Review and The Increment of Sprint 4. When the session names a facilitator, the band adds their name and facilitating. The facilitator is a label. It gives no extra right. While the session is open, the band says Open — feedback captured here converts to backlog items in one click. Otherwise it says This session is closed. Its record stands as it was.

Before the project holds a review, the screen shows the title and this text: No Sprint Review has been held yet. It presents the Increment — everything the sprint got to Done — so it has nothing to show until a sprint has run.

The screen has two columns. The wide column holds Done this sprint, Carried over and Feedback. The narrow column holds The Increment, Attendees and Notes.

Nothing on this screen refreshes on its own. Each part refreshes after your own action on that part. To see the work of a colleague on a part you did not touch, reload the page.

The screen reports a failure in three places. A failed card, a failed summary and a failed switch show the reason in one line under the band. A failed notes save shows it inside Notes, above the blocks of other people. A failed attendee change shows it inside Attendees, above the list.

Open and close the session

No screen creates, opens, closes or cancels a Sprint Review. The product creates and opens one only through its API. The request names one sprint and needs Run sprints on the team that owns that sprint. The screen shows a session that already exists, in the state it is in. The Daily Scrum is the one session you start and close from a screen. See The board and the Daily Scrum.

The product saves the setting Book the Sprint Review automatically, but does not act on it. The product sends no email about a review and no reminder message. You can still add a stakeholder to the guest list on this screen. That person gets no message from the product, so tell them yourself.

The Increment

NeedsView view

The product does not store the contents of the Increment. It computes them each time the page loads, from the items in the sprint at that moment.

Done this sprint

Every item in the sprint with the status Done. This is the Increment.

Carried over

Every item in the sprint with any other status.

Each section shows a count. Each row shows the item's key, such as PROJ-12. When Show an imported system’s ID is on, a row with an external id shows that id instead, and a row with none keeps its key. The row also shows the item's name and, when it has one, the name of its assignee. An item with no name shows Untitled. Rows are in item-number order.

A row is not a link. To open an item, go to the Product Backlog. See The Product Backlog.

A row in Done this sprint also shows a pill such as 3/3 Done. The first number is how many active Definition of Done criteria the item meets. The second is how many the project has. A retired criterion counts in neither number. The pill stands out until the item meets every criterion. When the project has no active criteria, there is no pill.

Somebody with Manage the project keeps the list of criteria on the project screen. See Project settings. Somebody with Write items ticks each criterion in the item panel. See Backlog items.

A row in Carried over shows a status pill instead, such as To Do or In Progress. The status is why the item did not reach the Increment.

An empty Done this sprint says Nothing reached Done this sprint. That is the review’s first subject, not a gap in the screen. An empty Carried over says Nothing carried over.

The Increment summary

NeedsRun sprints sprint_run

The section The Increment starts with the box Increment summary. Its placeholder is What was built, written for stakeholders. People without Run sprints see the summary as text instead, or No summary written yet.

1. Click in Increment summary.
2. Type the summary.
3. Click elsewhere, or press Tab.

The product saves when the box loses focus. There is no save button. A summary holds up to 20,000 characters. If you leave the box empty, the product clears the summary rather than storing a blank. You can write the summary while the session is open, closed or scheduled. It belongs to the sprint's Increment, not to the session.

The box fills once, when the page loads, and keeps your text after a save. A summary from somebody else appears after you reload the page.

Demoed and Released

NeedsRun sprints sprint_run

Two switches follow the summary: Demoed and Released. The hint under them says Demoed and Released are separate. An Increment can be shown without being shipped. People without Run sprints see the switches and cannot change them.

1. Click Demoed to record that the team showed the Increment to stakeholders.
2. Click Released to record that the Increment shipped.
3. Click a switch again to clear it.

Each switch is its own claim, and one never sets the other. The product records the moment you set a switch. If you set a switch that is already set, the first moment stays. When you clear a switch, the product removes the moment. The switches work on any session status.

When you set a switch, or save the summary, the product reads the Increment again. Done this sprint and Carried over then show the items as they are at that moment.

Feedback

NeedsWrite in Scrum Events event_write

The section Feedback holds what stakeholders said, one card each. Its hint reads What stakeholders said, and what the backlog should do about it. Before the first card, it says Nothing captured yet. Each card shows its text and the name of the person who wrote it, or Someone when they have no display name.

The box Add feedback is under the cards. Its placeholder is What did a stakeholder say? It is absent for people without Write in Scrum Events, and absent for everyone while the session is not open.

1. Type what the stakeholder said in Add feedback.
2. Click Add feedback.

The card appears after the last one, the box clears and the count rises. A card holds up to 2,000 characters. The product disables the button until the box holds text. The box clears whether the product saved the card or refused it. If the screen shows a refusal, type the card again.

The product also reads every card again, so the new cards of a colleague appear too.

Edit or remove a card

NeedsWrite in Scrum Events event_write

You can edit and remove your own cards. With Manage the project you can also edit and remove the cards of anybody else. On any other card, Edit and Remove are absent. Both are absent for everyone while the session is not open.

1. Click Edit on the card.
2. Change the text in Edit feedback.
3. Click Save.
4. To keep the old text, click Cancel.

One card is in edit mode at a time in your own browser. If you save an empty box, the product blocks it: Invalid request body.

After any refused save, the editor closes and the card shows its old text. Your change is gone. Click Edit again and type the change again.

To remove a card, click Remove. There is no confirmation and no undo. The card disappears and the count falls. When you remove a converted card, the backlog item stays. The product removes only the link from the card to it.

Convert feedback into a backlog item

NeedsWrite items item_write

Each card that is not yet converted has a button Convert to item. It needs Write items, Write in Scrum Events and an open session. Without all three the button is absent.

Write in Scrum Events does not include Write items, so a guest who can write feedback cannot always create the backlog item. See Roles and permissions.

1. Click Convert to item on the card.

There is no other field to complete, and you cannot choose the item type. The product creates the item and links the card to it in one step. The new item:

• Has the type Task. A project can rename that type, and the new item then carries the new name.
• Has the status Draft.
• Sits at the end of the default phase of the project, in no sprint.
• Takes its name from the text of the card on one line. The product cuts a name over 200 characters and ends it with ….
• Takes as its description one line, Feedback from the Sprint 4 Review. then a blank line, then the full text of the card.

The card then shows a pill with the item's key, such as PROJ-42, in place of the button. The pill links to the Product Backlog screen, not to the item itself. The pill stays after the session closes. The item carries no link back to the review. Its description is the only trace of its source. See The Product Backlog.

Attendees

NeedsView view

The section Attendees is the guest list. Stakeholders you invite appear here with their capacity. Members of the team that owns the sprint never appear on the list. They can already take part in the session. Before the first invitation, the list says The owning team are implicit participants and carry no row here. Everyone who can see the project can read the list.

A guest with the capacity Participant can write feedback and notes, if they also hold Write in Scrum Events. An observer reads. Every rule of the guest list, and each message it shows, is in Scrum Events.

Keep the guest list

NeedsRun sprints sprint_run

The controls are absent for people without Run sprints.

• Invite someone opens a picker over the members of the organization. It is absent on a closed session.
• Each row has a capacity select, Observer or Participant, and an attendance select, Not recorded, Present or Absent. A change saves at once, on an open or a closed session.
• Remove deletes the row of the person. It is absent on anybody recorded as Present.

Notes

NeedsWrite in Scrum Events event_write

The section Notes holds one block per person. The blocks of other people appear first, under the name of the author. Your box is Your notes, with the placeholder Everyone writes their own block. It is absent for people without Write in Scrum Events, and absent for everyone while the session is not open.

Your notes opens with the block you saved before.

1. Type in Your notes.
2. Click Save my notes.

The product saves on the click, not on each keystroke. A block holds up to 20,000 characters. If you save an empty box, the product deletes your block. Notes need the same rights as feedback: membership of the team that owns the sprint, or the capacity Participant. The full rule is in Scrum Events.

The one conflict is with yourself, when the session is open in two tabs. The screen then says You have this session open somewhere else, and it has newer notes. It reads the notes again and keeps your draft in Your notes. See Editing conflicts.

Calendar file

NeedsView view

This screen offers no calendar file, and no other screen links to one. The product still serves a Sprint Review as a calendar file when the session has a scheduled start and a scheduled end. Everyone who can see the project can read that file. See Scrum Events.