Run your first sprint end to end

Estimate with planning poker, prepare the sprint, start it, run the daily, then close with the Sprint Review and the retrospective.

Plan

All plans

Required permission

Sprints › CreateDefault: Product Owner, Scrum Master, plus the project owner and admins.

This walkthrough assumes a backlog is already filled in: see Generate a backlog with the Launchpad or Import a backlog.

#1. Estimate the tickets

1. In Tickets, click Planning Poker, then start a session.
2. Choose the ticket to estimate: everyone votes at the same time, without seeing the others' cards.
3. Reveal the votes, discuss the gaps, then choose the story points to assign. The estimate is saved on the ticket.

In detail: Estimate with planning poker.

#2. Create the sprint

In Sprints, click Create Sprint, then fill in Sprint name, Sprint goal, Start date and End date.

#3. Prepare the sprint (Sprint Planning)

1. On the sprint card, click Sprint Planning.
2. Tick the Preparation checklist: prioritised backlog, refined tickets, estimated velocity.
3. Present the Sprint goals and set the Team capacity.
4. Add tickets from the Available backlog and adjust their story points.
5. Click Finish planning. Unestimated tickets count as 0 points: Manifst warns you before you confirm.

In detail: Prepare a sprint.

#4. Start the sprint

Click Start. Only one sprint can be active at a time. The team then follows progress in Kanban and on the dashboard.

#5. Run the daily

1. In Sprints, switch to the Daily view, then click Start the daily.
2. Choose who speaks, then Start the round. Manifst shows each person's tickets and the blockers to sort out today.
3. Close the daily: the report is emailed to the project members (except observers), and can also be saved in MyDoc. See Run the daily.

#6. Complete the sprint

Click Complete on the active sprint's card. Unfinished tickets move to the next sprint if there is one, otherwise they go back to the backlog.

#7. Sprint Review and retrospective

• Sprint Review: the sprint's results (delivered, carried over, cost, burndown). The Product Owner or the Scrum Master gives a verdict on the goal: met, partially met or not met.
• Retrospective: three columns, What went well, What caused problems and Improvement actions. Poll the team collects anonymous contributions for a limited time; Analyze with AI summarises them. Send the report emails it as a PDF to the project members (except observers and PMO).

In detail: Run the Sprint Review and Run the retrospective.