Beruflich Dokumente
Kultur Dokumente
SCRUM FOUNDATIONS
Hiren Doshi | hirendoshi@practiceagile.com | (+91) 96193 22001 @ScrumDotOrg v 4.3.1 © 1993 – 2018 Scrum.org All Rights Reserved 1
“If you haven’t found it yet, keep looking. Don’t settle.
As with all matters of the heart, you’ll know when you
find it.”
- Steve Jobs
1
Introductions
• Introduce yourself
• Have you used Scrum before?
• What’s your background:
• Development?
• IT?
• Other?
10
minutes
www.scrum.org/courses
v 4.3.1 © 1993 – 2018 Scrum.org All Rights Reserved 8
Professional Scrum Foundations Course
PURPOSE AUDIENCE
2
Kickoff
60
minutes
• Simple
everything is known
Scrum
• Complicated
Thrives Here
• Complex
more is unknown than known
• Chaotic
very little is known
Source: Ralph Stacey, University of Hertfordshire
PREDICTIVE EMPIRICAL
5
minutes
Adaptation Inspection
Scrum (noun):
A framework within which people can
address complex adaptive problems, while
productively and creatively delivering
products of the highest possible value.
www.scrumguides.org
Where is the value of the Scrum Values for your daily work?
Scrum Values
10
minutes
Traditional Development
Plan Analyze Design Code Test Release Review
Scrum
Analyze Analyze Analyze Analyze Analyze
Review/Reflect
Review/Reflect
Review/Reflect
Review/Reflect
Review/Reflect
Design Design Design Design Design
Plan
Plan
Plan
Plan
Plan
Code Code Code Code Code
Test Test Test Test Test
Release Release Release Release Release
5
minutes
• Product Owner
• Development Team
• Scrum Master
Artifacts
• Product Backlog
• Sprint Backlog
• Increment
Events
• Sprint
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
Scrum Master
Promote and support Scrum
Removing impediments
5
minutes
5
minutes
May Select
(hire) Product Owner
Development Team
Feature
Constraints Behaviors
Definitions
Non-
Desirements functional
Requirements
v 4.3.1 © 1993 – 2018 Scrum.org All Rights Reserved 42
Sprint Backlog Holds the Plan for the Current Sprint
10
minutes
• Container Event
Sprint • 30 Days, or less, in duration
Allows flexibility in
delivering the • Allows wiggle room for exact implementation of PBIs
Increment
Is fixed throughout • As the Development Team works, it keeps this goal in mind
• The Development Team inspects and adapts their plan to
the Sprint meet the Sprint Goal in every Daily Scrum
5
minutes
5
minutes
“The Scrum Guide” (Ken “Scrum – A Pocket Guide” • “Scrum and XP from the
Schwaber, Jeff Sutherland) (Gunther Verheyen) trenches” (Henrik Kniberg)
5
Sprint Two
70
minutes
Requirements
Design
Code
Test
• Managing the use and adoption of Scrum by the Scrum Team and
within the organization
• Serving and coaching the Scrum Team
• Embodying agility for all to see
5
minutes
Question: What is missing? How is it transparent? Who
should attend? What’s the time-box?
Sprint Less than 3 hours Less than 3 hours Less than 3 hours
3 hours
Retrospective (~2 hours 15 mins) (~1 hour 30 mins) (~45 mins)
• Product Owner
• Development Team
• Scrum Master
5
minutes
1 What
Analyze, evaluate and select
Product Backlog Items for Sprint.
Sprint Goal gives direction
2 How
Decompose into actionable plan
Enough work is decomposed
• Share commitments
• Identify impediments
• Create focus
• Increase and maintain
situational awareness
Development Team
Product Owner Shares Everyone
Shares
•What was done •The actual Increment •Provides and hears
•What wasn’t done of software feedback
•State of the Product •What happened in
Backlog the Sprint
•Projections of likely •How problems were
release targets addressed and the
effect on the
Increment
This is a
collaborative Product Current Business
Sprint Backlog Increment Conditions
working session,
not a
demonstration. Review, discover & rearrange info
• A discussion of:
• The Scrum process
• Scrum Team member behaviors
• Tools used and needed
• Expanding the definition of “Done”
• To find actionable improvements
• The Scrum Team can enact next Sprint
• To adapt common practices and techniques
• To increase the DoD
- Norm Kerth,
Project Retrospectives: A Handbook for Team Reviews
What worked?
What didn’t work?
What will we commit to
do in the next Sprint?
• Refining means
• Planning the PBL to an actionable level of detail
• Maintaining a Rolling Backlog Projection
• Plan 10% of the Sprint capacity of the Development Team to be
spent on refining the Product Backlog
• Top ordered Product Backlog items are well understood and easily
selected in Sprint Planning
➔They are ‘Ready’
• In general the DoD is for the Increment and all Product Backlog
items
• Checklists for definition of “Done” at various levels and
checkpoints can be helpful
• Visit definition of “Done” in each Retrospective
140
120
100
80
60
40
20
0
Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
30
25
Functionality Delivered
20
15
10
0
1 2 3 4 5 6 7 8 9
Sprint
3
minutes
5
minutes
• Requires skill
• In the domain at hand
• In the constraints of the framework
• In the software development craft
• Skills needed in software teams using Scrum
• Scrum itself • Levels of testing
• The business domain • Mastery of development tools
• Useful technologies • Build and deploy automation
• Practices of software craftsmanship • Emerging architecture or design
• The science of user experience • Many, many more
• Languages and frameworks
5
minutes
3
minutes
•
•
Loose Coupling
User Acceptance Testing
•
•
Demo to customer
Dedicated QA resources
• Sprint Planning • Product Backlog
• Planning • Design
• Empiricism • Coding
• Collaboration • Testing
• Self-Organization • Automation
• Leadership • Deploying
• Communication • User Experience
• Transparency • Emergent Architecture
• In a multi-disciplinary
Development Team of
appropriate size, people need
to move beyond their areas of
specialization
• Task pairing and sharing grows
everyone
• Focus shifts from fulfillment of
individual duties to the overall
success of the team
5
minutes
Anything that:
• Impedes or slows a team’s progress
And
The Scrum
Master’s bread • Cannot be resolved by the team internally
and butter
70
minutes
9
Planning With Scrum
Daily
Plan
This
Sprint +1 Sprint
Other Next Sprint +2
Backlog Release
Items
Sprint
Planning
Refinement
Refinement
Together, we are
smarter than any
one of us.
- Japanese proverb
3
minutes
Experiment with options
for implementing
Feature Z.
Homer
13
Get ready to go
on vacation
5
Lisa
v 4.3.1 © 1993 – 2018 Scrum.org All Rights Reserved 129
1 2 3 5 8 13 21 34 55
Planning Poker
Homer
13
Get ready to go
on vacation
5
Lisa
v 4.3.1 © 1993 – 2018 Scrum.org All Rights Reserved 130
1 2 3 5 8 13 21 34 55
Planning Poker
Homer
8
Get ready to go
on vacation
5
Lisa
v 4.3.1 © 1993 – 2018 Scrum.org All Rights Reserved 131
Exercise
5
minutes
Planning Poker • Choose 3-5 PBIs of varying size your team has
already delivered.
1
• Choose 1 of medium size and label it as a 5.
• Estimate the other completed PBIs.
• Use the estimated items as a comparison point to
the items you are estimating.
5
minutes
10
minutes
Title: ...
As a . . .
I want . . .
So that . . .
Development Team
Alpha
Scenario: ...
Given . . .
Business Value - 13
When . . . Effort Estimate - 5
Then . . . ROI - 2.6
Improvement to User
Experience
• Risk
• Identify risk for items in the Backlog
• Do highest risk items first
Ordered in a way • Return on Investment
to maximize • Simple business value ranking system
value delivered • This gives a single number by which to rank
work
• Because the Product Owner says so
4.8
• Less subjective 4.3
2.3
1.7
0.0
.73
.04
question? Size: 1
Size: 8
• Average Team Velocity = 33 Size: 13
A
• Sprint Length = 2 weeks Size: 3
Size: 89
Size: 13
5
minutes
question? ? Size: 13
Size: 3
• Average Team Velocity = 18 Size: 13
5
minutes
Cone of Size: 2
50 Uncertainty Size: 8
Story Points
Size: 5
40
Size: 13
30 Size: 3
Size: 13
20
Size: 5
10 Size: 8
Size: 2
0
1 2 3 4 5 6
Sprint
PRODUCT BACKLOG
Release Plan
Sprint Plan
Daily Plan
“User Stories Applied” (Mike Cohn) “Agile Estimating and Planning” (Mike Cohn)
70
minutes
with Scrum
1 3 5
2 4 6
20
minutes
• Fill out the canvas for your organizational transformation
• Follow the boxes in order
Agile Transition
Backlog
15
minutes
Refining the Scrum • Who will be the Product Owner for this
Implementation Scrum Implementation Backlog?
Backlog
• Who will work with this Product Owner to
refine this backlog?
• Ideally, 1 person from each team in class
• Plus the highest ranking person in class
2
minutes
PRODUCT OWNER
SCRUM MASTER
v 4.3.1 © 1993 – 2018 Scrum.org All Rights Reserved 156
What is a Reasonable DoD For a First Sprint?
• Sprint Planning
• Daily Scrums
• Sprint Review
• Sprint Retrospective
12
Closing
P
v 4.3.1 © 1993 – 2018 Scrum.org All Rights Reserved 165
Exercise
It’s Your Call I’ve had 2 great days of discovery about Scrum. But,
when I go back to work I still have to deal with many
old ways of working (dates, actuals, predictions).
10
minutes
Over the past 2 days, you have learned the importance of inspection,
adaptation, and fast feedback cycles. To reinforce those concepts, if
you attempt the Professional Scrum Master I (PSM I) certification
assessment within 14 days and do not score at least 85%, you will be
granted a 2nd attempt at no further cost.
• Test your basic knowledge of Scrum and learn from immediate feedback by
taking an Open assessment:
www.scrum.org/assessments/open-assessments
• Use the Open assessments to prepare for Level I assessments