cPrime Training Center www.cprime.com/ctc Certified ScrumMaster 1 All slides 2013 Roger. W. Brown Certified ScrumMaster Course Instructor – Roger Brown CST, CSC 2 Course Objectives You will learn about The Scrum framework Common Scrum practices ScrumMaster responsibilities and skills And you will be eligible for ScrumMaster Certification 3 CSM Class Backlog Welcome Agile Principles Scrum Execution Flow and Focus Scrum Planning User Stories Prioritization Estimation Long Term Planning Class Project ScrumMaster Duties Team Growth Scaling Scrum Up and Out Scrum Adoption Certification Q & A Homework Technical Practices Scrum Enhancers Scrum Framework ScrumMaster Skills Empirical Process 4 Empirical Process • Agile success relies on “Empirical Process” • Improvement comes from a continuous learning cycle we call “Inspect and Adapt”. 5 Continuous Improvement Plan Do Check Act Deming Cycle Empirical Process Transparency, Inspect and Adapt 6 notes 6
18
Embed
cPrime Training Center cPrime Training Center Certified ScrumMaster 2 7 Agile Principles • Agile software development implements Lean principles and dynamics. • Scrum ...
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
cPrime Training Center
www.cprime.com/ctc
Certified ScrumMaster
1
All slides 2013 Roger. W. Brown
Certified ScrumMaster Course
Instructor – Roger Brown CST, CSC
2
Course Objectives
You will learn about
The Scrum framework
Common Scrum practices
ScrumMaster responsibilities and skills
And you will be eligible for ScrumMaster Certification
3
CSM Class Backlog
Welcome
Agile Principles
Scrum Execution
Flow and Focus
Scrum Planning
User Stories
Prioritization
Estimation
Long Term Planning
Class Project
ScrumMaster Duties
Team Growth
Scaling Scrum Up and Out
Scrum Adoption
Certification
Q & A
Homework
Technical Practices
Scrum Enhancers
Scrum Framework
ScrumMaster Skills
Empirical Process
4
Empirical Process
• Agile success relies on “Empirical
Process”
• Improvement comes from a continuous
learning cycle we call “Inspect and
Adapt”.
5
Continuous Improvement
Plan
Do Check
Act
Deming Cycle
Empirical Process Transparency,
Inspect and
Adapt
6
notes
6
cPrime Training Center
www.cprime.com/ctc
Certified ScrumMaster
2
7
Agile Principles
• Agile software development implements
Lean principles and dynamics.
• Scrum is one form of Agile, designed
initially for software development but
applicable to other kinds of work.
8
Manifesto for Agile Software Development 2001
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
www.agilemanifesto.org
Agile Manifesto
9
Agile Software Development
Team Based Incremental Iterative Frequent Delivery Fully Visible Production Quality Value Driven
10
Agile “Brands”
XP development
practices
Kanban workflow management
Scrum collaboration
framework
Agile
Lean
11
When to Use
Scrum Lean Startup
Waterfall Kanban
Solu
tio
n
Problem
known unknown
kn
ow
n
u
nkn
ow
n
12
notes
12
cPrime Training Center
www.cprime.com/ctc
Certified ScrumMaster
3
13
Scrum Framework
• Scrum has 4 meetings and 3 artifacts
• Scrum has 3 roles that share the
responsibility of creating value in small
increments
• The roles complement each other to
create a balanced team
14
Scrum Framework
Potentially Shippable Product
Increment
Sprint Backlog
Product Backlog
Release
Planning
Sprint
Planning
Sprint
Review Sprint
Retrospective
Daily
Scrum
1-4
weeks
15
The Scrum Team
Desired Features
Product Owner
Development Team
Product
ScrumMaster
16
Product Owner
Maximizes the value of the work done
o Sets Vision o Manages Backlog o Elaborates Features o Decides Release Dates o Reviews Work
17
o 7 ± 2 o Cross functional o Full-time o Self-organizing o Empowered
Development Team Member
Develops the product with high quality
18
ScrumMaster
o Facilitate o Protect o Coach o Teach o Administer
Helps the team be awesome
cPrime Training Center
www.cprime.com/ctc
Certified ScrumMaster
4
19
notes
19 20
Scrum Execution
• Scrum organizes work into 1-4 week time
boxes called Sprints
• Each Sprint has 4 primary meetings
• The bulk of the time is spent creating
value in the form of a product
21
Sprint Planning Meeting
Product Backlog
Sprint Backlog
Pri
ori
ty
Goal 1: What?
• Which PBIs can we commit to? • What is our Sprint Goal? Ex. Build the shopping cart
Goal 2: How?
• What tasks can we identify for each story? • How long do we think each will take?
Attended by • Product Owner, Development Team, ScrumMaster • Other interested stakeholders
Time-box is 4 hours for a 2
week Sprint
22
Sprint Time Box
S1
1-4 weeks
Steady cadence, fixed length Abnormal Termination If the Sprint Goal cannot or should not be reached for
unexpected reasons, stop and plan a new Sprint
Focus No one can change the Sprint plan except the Scrum Team to add or
remove a PBI
S2 S3 S4
23
Daily Scrum
15 Min
The Three Questions What did you do yesterday? What do you plan to do today? Is anything blocking you?
24
Sample Sprint Backlog
User Story Task Work Remaining (hours)
Story Task T F M T W T F M T W T
Create Account Create home page with “create
account” link 8 8 4 2 0
Create Account Set up integration server 6 4 0
Create Account Create sign-up form 3 1 0
Create Account Create user table 2 2 0
Create Account Create user class with “create”
method to populate user table 4 4 6 1 0
Create Account Test user flow 1 1 1 1 1 0
Create Account Test failure cases 6 6 6 6 6 3 0
Login Add login form to home page 2 0
Login Create user class factory 2 2 0
Login Create error logic for bad login 2 2 2 2 2 2 2 2 0
Login Test Error Cases 2 2 2 2 2 2 2 2 2 0
Admin Add link to admin page 1 1 1 1 1 0
Admin Add user list report to admin page 4 4 4 6 6 6 4 2 0
• Attendees • Product Owner, Development Team, ScrumMaster
• Any other stakeholders
• Last day of Sprint • ~2 hours for a 2 week sprint
Preparation • Who will show what? • Deploy to a preview server • Any documentation needed? • Update and show release burnup chart
2 Hours
Show actual running
code!
26
Sprint Retrospective
• Team meets privately
• Goal is process improvement
• Format
• Gather Data
Reflect on what worked well, what didn’t
• Generate Insights
Discuss results and new ideas
• Decide Action Items
Consider adopting new practices
Stop doing things that are not working
1.5 Hours
Start Stop Continue
Keep it interesting • Appreciations • Food • Variety
27
notes
27 28
Scrum Planning
• Scrum planning is continuous
• Scrum planning happens at 5 levels, each
with a different time horizon
• The Product Backlog is the primary
source of work to be completed and
value to be delivered
29
Value Driven
Estimates
Features
Schedule Cost
Plan
Driven
The Plan creates
cost/schedule estimates
Waterfall
The Vision creates
feature estimates
Schedule Cost
Features
Value / Vision
Driven
Agile
Source: Sliger and Broderick “The Software Manager’s Bridge to Agility”
Constraints
30
5 Levels of Planning
Strategy
Portfolio
Vision
Roadmap
Release
Sprint
Day
P1 P2 P3 P4 P5
Product Backlog
Release 1 Release 2 Release 3
s1 s2 s3 s4 … sN
Scru
m P
lan
nin
g
cPrime Training Center
www.cprime.com/ctc
Certified ScrumMaster
6
31
• The Big Picture of how the product creates value
• Aligns team and business to the same goal
Product Vision
What is the name? Who is the target customer? What are the key benefits? What are the differentiating features?
32
Product Backlog
• Dynamic set of items to be done
• Prioritized
• Constantly in flux as the situation changes
Story
Story
Story
Spike
Story
Refactor
Story
Defect
Process Change
items are removed
priorities change
items are added
33
notes
33 34
User Stories
• User Stories are simple descriptions of
desired functionality
• User Stories have two attributes that are
helpful for planning: size and priority
• Stories are elaborated just-in-time for
implementation
35
User Story Template
As a <user role>, I can <do something> so that <I get some value>.
Card – Conversation - Confirmation
36
Sample User Stories
As a student, I can get a degree on-line so that I do not have to move near a college campus
As an online student, I can print a copy of my last report card in case an employer asks for it
As a degree candidate, I can see which courses I still need to satisfy my major so I can plan my next term
As a professor, I can get student test summary reports so that I can assess my teaching effectiveness
cPrime Training Center
www.cprime.com/ctc
Certified ScrumMaster
7
37
Backlog Hierarchy
Epic User Story Task Task Task Task
User Story Task Task Task Task
User Story Task Task Task Task
Product Backlog
Sprint Backlog
Business Goal
Planning Implementation
38
Where are the details?
(front)
Story 1: Home Page As a prospective student, I can view the college services so that I can decide if I want to apply.
(back)
Story 1 Acceptance Criteria [ ] Uses standard design layout [ ] Shows testimonials [ ] Introduces degree programs and top 5 majors [ ] Lists 5 most popular courses [ ] Call to action: Get our brochure [ ] Call to action: Enroll Today
Automated Tests
Speclet • formula • UI design • algorithm • business rules
39
notes
39 40
Prioritization
• Priorities help the Scrum Team decide
what to do next
• Priorities help with long term planning
• Prioritization can be done in many ways,
based on many criteria
41
Prioritization - MoSCoW
o Business value
o New knowledge
o Risk/Complexity
o Desirability
42
Story Map
Epic
I can browse by
department
I can search by subject
I can register
I can read content
I can browse by
title
I can unregister
I can browse by professor
I can join a waitlist
I can take tests
I can search by date offered
I can search by major
I can take classes on-line
Browse Search Register Attend Reports
I can do homework
I can print my
transcript
I can see my grade for a class
I can browse by popularity
Theme
Must
Should
Could
Pri
ori
ty
Smaller stories give more options for prioritizing for max value
42
I can print my
schedule
I can print my report
card
I can chat with
classmates
cPrime Training Center
www.cprime.com/ctc
Certified ScrumMaster
8
43
notes
43 44
Estimation
• Agile estimation is done at both the high
level and the low level
• Estimates are used for planning and for
tracking progress
• Estimates are done quickly, by the
Development Team
• Estimates are not commitments
45
Why Estimate?
Story Points • High Level
• Compare one story to another
• Forecast Releases and Sprints
Task Hours • Low Level
• 1-8 hours for a Story element
• Refine Sprint plan
• Track Sprint progress
46
Estimation Basics
Quick
Story 1: Home Page As a prospective student, I can view the college services so that I can decide if I want to apply.
2 Story 17: Major Progress
As a degree candidate, I can see which courses I still need to satisfy my major so I can plan my next term
5
Quick
Relative
Guess
Done by Team
More than 2x effort required
47
Affinity Estimating
Groups of 2-3 people choose some stories
Put in column with similar sized stories
Team members
can move stories
Visual grouping for quick comparisons
1 2 3 5 8 13 20
Start with numbers
or arrange by size
first
48
Velocity
5
12
27
32
36 38
40 37 38
40
0
5
10
15
20
25
30
35
40
45
1 2 3 4 5 6 7 8 9 10
Sto
ry P
oin
ts C
om
ple
ted
Sprint
Team Velocity
How many story points can the Team complete in a Sprint?
Patience is advised. “A dead ScrumMaster is no help to anyone.”
- Ken Schwaber
98
Scrum Values [Schwaber 2002]
• Commitment
• Focus
• Openness
• Respect
• Courage
The Scrum Team commits to doing their best
to achieve Sprint and Release goals. In turn,
they have the authority to make the decisions
necessary for success. The organization
allows the Team to focus on just the work they
have committed to. Openness provides the
visibility we need for maximum information on
status, progress and feedback when making
decisions. People are more productive in an
environment of mutual respect and trust. It
takes courage to make the change from
individual effort to Team contribution and to be
willing to say “no” when necessary.
99
notes
99 100
Q & A/Parking Lot
101
Certification
• You are almost there!
• What are the other certifications?
• What do I do next?
102
Certified Scrum
Professional
Scrum Certification Options
Theory Practice Guide
Certified ScrumMaster
Certified Scrum
Product Owner
Certified Scrum
Developer
Certified Scrum Trainer
Certified Scrum Coach
The Scrum Alliance is a nonprofit organization committed to delivering articles, resources, courses, and events that will help Scrum users be successful.
www.ScrumAlliance.org
cPrime Training Center
www.cprime.com/ctc
Certified ScrumMaster
18
103
Closing
o Action Items
o Class Evaluation
o Class Picture
o Graduation Ceremony
104
actions
104
Things I can do this week to make my work life better: Things I can do this week to make my work life better: