7. Introduction to Scrum
Product owner
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.
7
8. Introduction to Scrum
Scrum Master
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
8
9. Introduction to Scrum
Scrum Team
Typically 4-9 people
Cross-functional
Members should be full-time, no multi-tasking
Teams are self-organizing
Membership can change only between sprints
9
11. Introduction to Scrum
Sprint Planning Meeting
What?: 4hrs
How?: 4hrs
Product Backlog
Team Capabilities
Sprint Goal (what?)
Sprint Planning
Business Conditions
Meeting Sprint Backlog (how?)
Technology
Current Product
11
12. Introduction to Scrum
Sprint Planning Meeting (cont.)
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
12
13. Introduction to Scrum
Product Backlog
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’…
13
14. Introduction to Scrum
Sprint Backlog
• 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
14
15. Introduction to Scrum
From Sprint Goal to Sprint Backlog
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
Returns
Gift vouchers
Payments
15
17. Introduction to Scrum
Daily Scrum
Max. 15 minutes
What did I do yesterday?
What will I do today?
Is there anything in my way?
17
18. Introduction to Scrum
After the sprint
Sprint Review
• Present what team accomplished.
• Demo new features developed or underlying architecture.
• Invite whole world.
2 hours
Sprint Retrospective
Whole team discusses the results of last sprint
• Start doing
• Stop doing
3 hours
• Continue doing
18
20. Introduction to Scrum
Scrum is Agile
Delivers highest customer value first.
Focuses on planning than on plan.
Builds working software at rapid and repetitive pace.
Builds Self-organizing teams
20