Scrum projects are organized in short iterations (Sprints), during which the team plans, executes and reviews work. Each Sprint adds incremental value to the end goal.

Task Size

Tasks can be of varying sizes, however no task should take longer than the duration of the Sprint. It is recommended to split larger tasks into smaller ones.

Task Assignment

Team members self-assign tasks by pulling them from Sprint Backlog.

New Tasks In Iteration

Once a Sprint has started, no new tasks can be added.


Product Owner

represents client interests and prioritizes Product Backlog
Core responsibility - Communication

Scrum Team

Cross-functional team of professionals that self organizes to meet the Sprint goal.
Core responsibility - Delivering value

Scrum Master

facilitates the Scrum application and helps the organizational transition.
Core responsibility - Scrum application


Scrum iterations are called sprints. Planned and run one at a time, they ally last     1-4 weeks



Team estimates task size during Sprint Planning. This can be done in hours or Story Points.

Task Size

First column on the board that holds all the prioritized epics. and represents a project plan. Curated by PO.

Product Backlog

Second column on the board that holds all tasks planned for the current Sprint. Curated by the Scrum team.

Sprint Backlog

A short description of a feature.
that a client wants. Usually
As a.. I want.., so that…

User Story

A large user story that cannot be delivered as defined in one itera tion. Usually divided into smaller user stories.


A measuring unit to estimate task duration. Each team decides how much time 1 story point stands for.

Story Point

Shows how the number of uncompleted tasks decreases over time. Can indicate issues within the process.

Burndown Chart


Sprint – 1-4 week iteration during which a Scrum team delivers a potentially releasable product increment.
Sprint Planning – 8 hour session where the PO and Scrum Team decide what will be achieved in the next Sprint.
Daily Scrum – a 15-minute meeting for a team member to present what is done, what is planned, and how this helps the goal
Sprint Review – 4-hour meeting for the Scrum team, PO, and the stakeholders to discuss what was done during the Sprint and gather feedback.
Sprint Review – 4-hour meeting for the Scrum team, PO, and the stakeholders to discuss what was done during the Sprint and gather feedback.
Sprint Retrospective – 3-hour discussion between the Scrum Team and the SM on how the working process could be improved.

Scope Limits

The amount of work the team is going to do is limited by the duration of the Sprint.


Product Backlog is used to prioritize user stories and give clear direction to the team.


Usually combined out of 4 sections:
1.Product Backlog for User Stories
2.Sprint Backlog for planned tasks
3.Doing for the tasks in progress
4.Done for completed tasks