Know SCRUM

1. Planning new project with Scrum

Product development begins with tons of feature requests, risks, product requirements and later with the bugs. All of these assets are written in one place typically called Product Backlog.

Product Backlog is managed by Product Owner, who is responsible for assets prioritizing and grouping into releases.

Release is completed collection of assets that are deployed to customers.

2. Estimation

One of the important attributes of the story is "size". This is an amount of the effort needed to get the story completed. Effort is typically defined in storypoints. Storypoints have no unit. Story point describes relative size of the story to other product story.

Storypoins Effort and the Storypoints

Storypoints are typically Fibonacci numbers. Developers estimates stories effort size using technique called Planning Poker^®.

Development process is divided into iterations with constant duration. Iteration in Scrum is called a Sprint (15-30 days).

Product Development

Product Backlog

Release A Release B

Sprint 1 Sprint 2 Sprint 3

Completed Completed To Do Checked Out Solved Completed

3. Sprint planning

Prioritized assets are selected for development into sprint during the sprint planning meeting. Product owner will choose assets that he wants to complete.

During the sprint planning developers will estimate duration of the story implementation. This will define plan to story completion.

After the definition of sprint effort and development duration, it is possible to calculate velocity. This is an indicator how much of the work is team able to develop in the given time.

Velocity

3. Daily scrum

After the sprint planning is completed, scrum master can start the sprint. Every developer updates the time remaining to complete stories and its tasks on story card daily.

In a daily meeting every developer has to response on following questions:

What did you do yesterday?
What will you do today?
Have you any problems?

Sprint status is tracked by burn down chart displaying remaining work vs. time. This chart displays two data series, ideal serie displaying the best, ideal, development progress. Second serie displays real progress computed from remaining work in the given sprint day.

Sprint burn down chart

4. Retrospective

The last day of the sprint is a day when team meet and answer three questions:

What went bad during the sprint?
What went good during the sprint?
What are your improvements ideas?

Every team member can vote for the best ideas. These ideas has to be implemented in the next sprint to improve quality of the work. This is the main goal of the retrospective.

Restrospective ideas

Trademarks

ScrumDesk overview

TOC

ScrumDesk principles