View
14
Download
0
Tags:
Embed Size (px)
DESCRIPTION
This material made to introduction about Scrum, a very famous software development process now.
Citation preview
LOGO
PowerPoint TemplateClick to edit subtitle style
Introduction to
SCRUMPresented by: Tan Tran
Logigear – DS – May 2011
2
Introduction to Scrum
Contents
Scrum Roles2
Question?4
Introduction to Scrum31
The Scrum Process33
3
What is Scrum?Introduction to Scrum
4
CharacteristicsIntroduction to Scrum
5
Scrum FrameworkIntroduction to Scrum
Roles : Product Owner, Scrum Master, Team
Ceremonies : Sprint Planning, Sprint Review, Sprint Retrospective,
Daily Scrum Meeting
Artifacts : Product Backlog, Sprint Backlog, and Burndown Chart,
Release Backlog
6
Scrum RolesIntroduction to Scrum
Scrum Master
Product owner
Team
Plan
Implement
TestDemo
Inspect&
Adapt
7
Product ownerIntroduction to Scrum
Define the features of the product
Decide on release date and content
Be responsible for the profitability of the product (ROI)
Prioritize features according to market value
Adjust features and priority every iteration, as needed
Accept or reject work results.
8
Scrum MasterIntroduction to Scrum
Represents management to the project
Responsible for enacting Scrum values and practices
Removes impediments
Ensure that the team is fully functional and productive
Enable close cooperation across all roles and functions
Shield the team from external interferences
9
Scrum TeamIntroduction to Scrum
Typically 4-9 people
Cross-functional
Members should be full-time, no multi-tasking
Teams are self-organizing
Membership can change only between sprints
10
How Scrum works?Introduction to Scrum
11
Sprint Planning MeetingIntroduction to Scrum
Sprint Planning
Meeting
Product Backlog
Team Capabilities
Business Conditions
Technology
Current Product
Sprint Backlog (how?)
Produ
ct O
wner
Scrum
Tea
m
Man
agem
ent
Custo
mer
s
Sprint Goal (what?)
What?: 4hrsHow?: 4hrs
12
Sprint Planning Meeting (cont.)
Introduction to Scrum
1st Part:
- Participants: Product Owner, Scrum Master, Scrum Team
- The PO present the top priority Product Backlog
- Determining the Sprint Goal.
2nd Part:
- Participants: Scrum Master, Scrum Team
- Creating Sprint Backlog
13
Product BacklogIntroduction to Scrum
Should include:
- Description
- Rank/Priority
- Complexity/Cost/Size (points or size X/M/L/XL or Fibonacci number
- Optional: business value ($...), owner, test, sample results…
Can be defined as a ‘User Story’, ‘Story card’, ‘User case’…
14
Sprint BacklogIntroduction to Scrum
• A subset of Product Backlog Items, which define the work for a Sprint
• Is created ONLY by Team members
• Each Item has it’s own status
• Should be updated every day
• If a task requires more than 16 hours, it should be broken down
• Team can add or subtract items from the list. Product Owner is not allowed to
do it
Code the UI
2 hours
Database design
1 hours
Service + JUnit
1 hours
DAO + DBUnit
1 hours
15
From Sprint Goal to Sprint BacklogIntroduction to Scrum
Code the UI
2 hours
Database design
1 hours
Service + JUnit
1 hours
DAO + DBUnit
1 hours
Scrum team takes the Sprint Goal and decides what tasks are necessary
Team self-organizes around how they’ll meet the Sprint Goal
‘Manager’ doesn’t assign tasks to individuals
‘Managers’ don’t make decisions for the team
Sprint Backlog is created
Gift vouchers
Returns
Payments
16
Sprint Burndown ChartIntroduction to Scrum
Progress
752 762
664619
304264
180104
200
100
200
300
400
500
600
700
800
900
Date
Rem
ain
ing
Eff
ort
in
Ho
urs
17
Daily ScrumIntroduction to Scrum
What did I do yesterday?What will I do today?
Is there anything in my way?
Max. 15 minutes
18
Introduction to Scrum
2 hours
Sprint Review
Sprint Retrospective
• Present what team accomplished.• Demo new features developed or underlying architecture.• Invite whole world.
Whole team discusses the results of last sprint• Start doing• Stop doing• Continue doing
After the sprint
3 hours
19
Introduction to Scrum
Scaling Scrum
Scrum of Scrum
Scrum of Scrum of
Scrum
20
Scrum is AgileIntroduction to Scrum
Delivers highest customer value first.
Focuses on planning than on plan.
Builds working software at rapid and repetitive pace.
Builds Self-organizing teams
LOGO
Next topic: Extreme Programming