Why you should adopt SCRUM
for Product Development
Innovate the processes

Increase Productivity

Improve Quality

Gain Morale

Give Visibility
Platform
Product
Desired 
Feature
#1 
Products
#2 
Scrum Team
Product 
Owner
Scrum
Master
Cross Functional Team
#3 
Backlog & StoryPoints
#4 
Sprint Planning
#5
Collaborative Workspace
#7 
 Stand UP
every day
#8 
BurnDown Chart
#9
Deliver the new feature
#11
Sprint Retrospective
Meeting
What is Scrum?
Team members
7 
+/-2
StakeHolders
PO
SM
Cross 
Functional 
Team
Product 
Backlog
The backlog contains only Desired User Stories and Features
All user stories refer to the Product
The Backlog is ordered by the PO
Sprint 1
Sprint 2
User Stories
Epics
MMF
1
2
3
5
8
13
21
...
Each User Story is estimated by the team
The team use story points to size each item of the Backlog
They use Fibonacci numbers not time
They do it as a team (SM+CrossFunt. team) using Planning Poker
Story Points
The backlog and its order
Sprint 1
Portion of the backlog that will be developed in the Sprint 1
Decide the lenght of the Sprint (1w, 2w, 4w)
Select the portion of the backlog that the team deem reasonably deliverable in the next Sprint
Self Organization
Elaborate and analize each User Story
Break down them into REQUIREMENTS
Transform requirements into tasks.
Estimate each task. Should be no longer than 8h.
Use post it with different colours per each skill or team member
Task 1 Title

Do this in this way in the better way
8 hours
Task 2 Title

Do this in this way in the better way
4 hours
Task 3 Title

Do this in this way in the better way
4 hours
Task 4 Title

Do this in this way in the better way
6 hours
Task 5 Title

Do this in this way in the better way
8 hours
Select from Backlog
Define requirements
Split into Tasks
Call the meeting
Task 1 Title

Do this in this way in the better way
8 hours
Task 2 Title

Do this in this way in the better way
4 hours
Task 3 Title

Do this in this way in the better way
4 hours
Task 4 Title

Do this in this way in the better way
6 hours
Task 5 Title

Do this in this way in the better way
8 hours
User Story 1

Very small description

Story Points: 13
Task 1 Title

Do this in this way in the better way
8 hours
Task 2 Title

Do this in this way in the better way
4 hours
Task 3 Title

Do this in this way in the better way
4 hours
Task 4 Title

Do this in this way in the better way
6 hours
Task 5 Title

Do this in this way in the better way
8 hours
User Story 1

Very small description

Story Points: 13
Story
To do
In Progr
Test
Done
Task 1 Title

Do this in this way in the better way
8 hours
Task 2 Title

Do this in this way in the better way
4 hours
Task 3 Title

Do this in this way in the better way
4 hours
Task 4 Title

Do this in this way in the better way
6 hours
Task 5 Title

Do this in this way in the better way
8 hours
User Story 1

Very small description

Story Points: 13
Task 1 Title

Do this in this way in the better way
8 hours
Task 2 Title

Do this in this way in the better way
4 hours
Task 3 Title

Do this in this way in the better way
4 hours
Task 4 Title

Do this in this way in the better way
6 hours
Task 5 Title

Do this in this way in the better way
8 hours
User Story 1

Very small description

Story Points: 13
Story
To do
In Progr
Test
Done
What I have achieved since the last meeting (yesterday)


What I will achieve before the next meeting (tomorrow)


Something/Anything is holding up my progress (‘impediments’)
PRODUCT
B
Feature
User Story 
2
Feature
User Story
1
StakeHolders
PO
Demostrate the feature
Each team member shows his/her work
Everyone can attend
Cross Functional Team
I have done this
SM
Review the final Burndown Chart. 
Review the team’s Velocity. 
Discuss what went well.
Discuss what could have gone better.
Decide what the team will do differently in the next Sprint? 
It allows team members to show what they’ve achieved and demonstrate their contribution to the product.

It allows all key stakeholders to see what’s been done, and provide valuable feedback on a regular basis, while there’s still time to take it on board.

It helps the team to stay focused on the deadline of the Sprint - no-one wants to show up at the Sprint Review with nothing useful to demo
How can we improve?
Estimated hours to complete
Sprint Days
Annotation
Annotation
Annotation
Set the Team Sprint goal
Plot Daily progress visually on a graph
Annotate with key events
Product 
Backlog
A
B
C
D
Sprint 
Planning
Delivered 
Features
A
B
Sprint 
Sprint 
Review
Scrum is an agile software development model based on multiple small teams working in an intensive and interdependent manner. 
Scrum is particularly adopted in product development requiring iterative process and continuous change in priorities.
The term is named for the scrum (or scrummage) formation in rugby, which is used to restart the game after an event that causes play to stop, such as an infringement.
meeting
meeting
Iteration 
From 1 to 4 Weeks
Designer
Developer
Content
Developer
Feature
User Story
1
#10
Sprint Review Meeting
#6 
Sprint
Sprint means:
- The team focus on 100% deliverables
- Practices (testing, usability test, etc..) are part of the job
- None and nothing can interfere with the team
Scrum Basics
The product Owner represents the stakeholders and the business
The Scrum Master maintains the processes and is responsible of the Scrum
The group that do the actual analysis, design, implementation, testing, etc.
A few Basics of Scrum
Develop Products
Not Projects

Each product is well defined with clear perimeters

Iteratively develop the product by adding features

Feature
DELIVERED
Author: 
Marco Chiaverini
marco@chiaverini.it