From PM to
ScrumMaster
What do I do now?
@JasonHallc
About Me
Jason Hall
• Coach & Agile Jump-starter
• 5+ years as Agile Coach, Trainer,
Facilitator, Practitioner
• 14+ years of past industry experience
as Product Owner, IT Project
Manager….blah.blah…blah…blah….bl
ah
But First…..
1. Standup and work with one or two neighbors.
2. What words/skills come to mind when you
think of Project Manager? Scrum Master?
3. Sit down, and write down, your
definitions.
4. Let’s share.
Approaches Compared
Lot of Uncertainty (Agile):
 Define : Iteratively
 Deliver : Incrementally
Pictures courtesy Jeff Patton and Leonardo da Vinci
Certainty / Plan Driven (Traditional):
 Define : Once up Front
 Deliver : All at the End
Scrum
The Most Popular Framework
 Transparency: shared definition of done and honest discussions to make
process and progress visible to those responsible for outcome.
 Inspection: frequently inspect artifacts and progress towards a goal.
 Adaption: adjust process, product or both.
Roles
 ScrumMaster
 Product Owner
 Team
Ceremonies
 Sprint Planning
 Daily Scrum
 Sprint Review
 Sprint Retro
Artifacts
 Product Backlog
 Sprint Backlog
 Burndown
Burndow
n
Scrum in a Nutshell
* Discovery is not explicitly part of the Scrum Framework
Initial Planning
Sprint Cycle
“Done”
Features
For this
Sprint
Product
Backlog
Sprint
Backlog
Initial
Discovery
*
Release
Planning
Sprint
Review
Daily
Scrum
Work
Sprint
Retro
Sprint
Planning
“Ready”
Features
For next
Sprint or two
Continuous Discovery
Backlog
Refinement
Led by Product Owner with help from Team
Led by Team
Product
Validation
In-Sprint
Feedback
Continuous Delivery
6
Project Manager and ScrumMaster
Compared
7
Project Manager
• Planning and Defining Scope
• Activity Planning and Sequencing
• Resource Planning
• Developing Schedules
• Time Estimating
• Cost Estimating
• Developing a Budget
• Documentation
• Creating Charts and Schedules
• Risk Analysis
• Managing Risks and Issues
• Monitoring and Reporting Progress
• Team Leadership
ScrumMaster
• Acts a change agent
• Ensure productivity
• Enables collaboration
• Leads Daily Scrum & Retrospective
• Addresses team issues
• Watches work to:
• Minimize disruption
• Minimize WIP
• Update burndown
• Address blocks & dependencies
• Ensures process adherence
Project Manager and ScrumMaster
Compared
8
Project Manager
• Planning and Defining Scope
• Activity Planning and Sequencing
• Resource Planning
• Developing Schedules
• Time Estimating
• Cost Estimating
• Developing a Budget
• Documentation
• Creating Charts and Schedules
• Risk Analysis
• Managing Risks and Issues
• Monitoring and Reporting Progress
• Team Leadership
ScrumMaster
• Acts a change agent
• Ensure productivity
• Enables collaboration
• Leads Daily Scrum & Retrospective
• Addresses team issues
• Watches work to:
• Minimize disruption
• Minimize WIP
• Update burndown
• Address blocks & dependencies
• Ensures process adherence
Who does that other stuff in Scrum?
9
Product Owner
• Owns Product Vision
• Leads Release Planning
• Defines features,
release date and
content
• Adjusts long term plan
based on feedback
• Prioritizes by economic
value
• Guide team with
information
• Makes trade-off
decisions
• Accepts or rejects work
ScrumMaster
• Acts a change agent
• Ensure productivity
• Enables collaboration
• Leads Daily Scrum &
Retrospective
• Addresses team issues
• Watches work to:
• Minimize disruption
• Minimize WIP
• Update burndown
• Address blocks &
dependencies
• Ensures process
adherence
The Team
• Makes detailed plans
• Story point estimates
• Sprint Planning /
Backlog
• Daily Scrum
• Leads execution and
delivery
• Focuses on steady
delivery of high quality
features
• Generates options for
Product Owner
• Manages own work
within Sprints
Scrum Roles
Tea
m
Outcome
Owner
Facilitative
Leader
How does a Scrum Master help with
Planning?
11
Sprint
Planning
Release
Planning
- Ensuring all voices are represented
- Ensures everyone’s voice is considered: PO, dev, test, architecture
Product Owner: Advocating for what top priority features to
work on next
Scrum Master: Advocates for sustainability of the system: reduction
of technical debt, refactoring,
Enforces team capacity limits
Ensures work being requested of the Team is Ready
Ensure all necessary Sub-tasks are created
Acceptance Criteria
User Story
On back…
• Design user interface
• Develop CSS/HTML
• Create database tables
• Create database indexes
• Created stored procedure
• Develop client side validation criteria
• Write test cases
• Code test fixtures
• Unit testing
• Etc.
As a user
I want to enter my personal
information
Estimate 3 points
Priority 1 (High)
• Address validated against
reference
• Phone number contains no
alpha characters, min. 10 digits
• Name and email address
required
• Basic UX, no validation, no save
• Database (tables, indexes, stored
procedures)
• UX with validation
• Save
• Help
Tasks
Sub Deliverables
12
Daily Scrum
Exercise Time! – The Daily Scrum
We are going to simulate a Daily Scrum.
• Five volunteers to represent Team Members
• One volunteer to represent a ScrumMaster
10 minutes
Daily Scrum (Standup) – The Scrum
Heartbeat
Mar
y
Venk
at
Rog
er
Lynn
Team Velocity Raptors
Oleg Emil
y
Type
Ready Build Verify Deployed
In Progress Done In Progress Done
Planned
Un-
Planned
Y
8
A
5
G
8
U
1
W
8
M
3
H
3
B
3
E
3
N
8
Q
2
Z
3
O
5
What will you complete by the next standup?2
What did you accomplish since the last standup?1
What’s in your way, and who/how can we help?3
3Questions
D
2
1. What is the team name?
2. What is the process that team is following?
3. What card or cards are blocked?
4. Who is working on a too many things?
Daily Scrum
Daily Scrum (Standup) Continued
Mar
y
Venk
at
Rog
er
Lynn
Team Velocity Raptors
Oleg Emil
y
Type
Ready (4) Build (6) Verify (4) Deployed
In Progress Done In Progress Done
Planned
Un-
Planned
Y
8
A
5
G
8
U
1
W
8
M
★★3
ASAP
H
3
B
3
D
2
E
★
6/6
3
N
8
Q
★
6/9
2
Z
3 ★★
ASAP
O
5 ★
6/4
1. What do the numbers 4, 6 and 4 at the top of the columns represent?
2. There is a bottleneck in this process, where is it and how do you know?
3. What are the highest priority cards and how do you know?
4. What changes in assignment could be made?
A Scrum Masters Reporting Tools – The
Burndown
17
Burndown Uh-ohs
18
Burndown Uh-ohs
19
A Scrum Masters Reporting Tools – The
Burnup
20
A Scrum Masters Reporting Tools –
Cumulative Flow Diagram
21
Response Time
Cycle Time
Lead Time
WIP
Sprint Retrospective at a Glance
Description
• SM guides team to
inspect Sprint & adapt for
future:
• Inspect people,
relationship, process, tools,
etc.
• Identify “pluses” and
“deltas”
• Refactor approach for
upcoming Sprints.
Duration
Half an hour to an hour
Attendees
ScrumMaster (leader), team,
optionally Product Owner22
Outputs:
 Process revisions
 Project or team structure revisions
 Quick hit action items
 Long term improvement items
 Understanding of team member perspectives
A retro relies on
double loop learning
So what’s a Scrum Master do now?
23
Planning
• Coordinate all
Ceremonies
• Advocate for
Sustainability
• Ensure all voices
present
• Help set
Structure/Cadence
Day to Day
• Remove blockers
• Ensure WIP Limits
• Enforce Sprint
boundaries
Retrospective
• Facilitate Inspection
• Track short/longer
term
• Process
Improvements
• Team Improvements
Forecasting &
Metrics
• Report on Progress
• Ensure Transparency
• Communicate Trade-
off decisions
Upcoming Events 2016
Our team wants to connect with you online!
Find us @LitheSpeed
Interested in Agile?
Become a Certified ScrumMaster
Upcoming Classes with LitheSpeed
President Sanjiv Augustine:
 June 23-24
 July 20-21
 August 24-25
Stop by the LitheSpeed booth to learn
more about Agile and Lean training,
coaching, and consulting.
Upcoming Events 2016

From Project Manager to Scrum Master

  • 1.
    From PM to ScrumMaster Whatdo I do now? @JasonHallc
  • 2.
    About Me Jason Hall •Coach & Agile Jump-starter • 5+ years as Agile Coach, Trainer, Facilitator, Practitioner • 14+ years of past industry experience as Product Owner, IT Project Manager….blah.blah…blah…blah….bl ah
  • 3.
    But First….. 1. Standupand work with one or two neighbors. 2. What words/skills come to mind when you think of Project Manager? Scrum Master? 3. Sit down, and write down, your definitions. 4. Let’s share.
  • 4.
    Approaches Compared Lot ofUncertainty (Agile):  Define : Iteratively  Deliver : Incrementally Pictures courtesy Jeff Patton and Leonardo da Vinci Certainty / Plan Driven (Traditional):  Define : Once up Front  Deliver : All at the End
  • 5.
    Scrum The Most PopularFramework  Transparency: shared definition of done and honest discussions to make process and progress visible to those responsible for outcome.  Inspection: frequently inspect artifacts and progress towards a goal.  Adaption: adjust process, product or both. Roles  ScrumMaster  Product Owner  Team Ceremonies  Sprint Planning  Daily Scrum  Sprint Review  Sprint Retro Artifacts  Product Backlog  Sprint Backlog  Burndown
  • 6.
    Burndow n Scrum in aNutshell * Discovery is not explicitly part of the Scrum Framework Initial Planning Sprint Cycle “Done” Features For this Sprint Product Backlog Sprint Backlog Initial Discovery * Release Planning Sprint Review Daily Scrum Work Sprint Retro Sprint Planning “Ready” Features For next Sprint or two Continuous Discovery Backlog Refinement Led by Product Owner with help from Team Led by Team Product Validation In-Sprint Feedback Continuous Delivery 6
  • 7.
    Project Manager andScrumMaster Compared 7 Project Manager • Planning and Defining Scope • Activity Planning and Sequencing • Resource Planning • Developing Schedules • Time Estimating • Cost Estimating • Developing a Budget • Documentation • Creating Charts and Schedules • Risk Analysis • Managing Risks and Issues • Monitoring and Reporting Progress • Team Leadership ScrumMaster • Acts a change agent • Ensure productivity • Enables collaboration • Leads Daily Scrum & Retrospective • Addresses team issues • Watches work to: • Minimize disruption • Minimize WIP • Update burndown • Address blocks & dependencies • Ensures process adherence
  • 8.
    Project Manager andScrumMaster Compared 8 Project Manager • Planning and Defining Scope • Activity Planning and Sequencing • Resource Planning • Developing Schedules • Time Estimating • Cost Estimating • Developing a Budget • Documentation • Creating Charts and Schedules • Risk Analysis • Managing Risks and Issues • Monitoring and Reporting Progress • Team Leadership ScrumMaster • Acts a change agent • Ensure productivity • Enables collaboration • Leads Daily Scrum & Retrospective • Addresses team issues • Watches work to: • Minimize disruption • Minimize WIP • Update burndown • Address blocks & dependencies • Ensures process adherence
  • 9.
    Who does thatother stuff in Scrum? 9 Product Owner • Owns Product Vision • Leads Release Planning • Defines features, release date and content • Adjusts long term plan based on feedback • Prioritizes by economic value • Guide team with information • Makes trade-off decisions • Accepts or rejects work ScrumMaster • Acts a change agent • Ensure productivity • Enables collaboration • Leads Daily Scrum & Retrospective • Addresses team issues • Watches work to: • Minimize disruption • Minimize WIP • Update burndown • Address blocks & dependencies • Ensures process adherence The Team • Makes detailed plans • Story point estimates • Sprint Planning / Backlog • Daily Scrum • Leads execution and delivery • Focuses on steady delivery of high quality features • Generates options for Product Owner • Manages own work within Sprints
  • 10.
  • 11.
    How does aScrum Master help with Planning? 11 Sprint Planning Release Planning - Ensuring all voices are represented - Ensures everyone’s voice is considered: PO, dev, test, architecture Product Owner: Advocating for what top priority features to work on next Scrum Master: Advocates for sustainability of the system: reduction of technical debt, refactoring, Enforces team capacity limits Ensures work being requested of the Team is Ready
  • 12.
    Ensure all necessarySub-tasks are created Acceptance Criteria User Story On back… • Design user interface • Develop CSS/HTML • Create database tables • Create database indexes • Created stored procedure • Develop client side validation criteria • Write test cases • Code test fixtures • Unit testing • Etc. As a user I want to enter my personal information Estimate 3 points Priority 1 (High) • Address validated against reference • Phone number contains no alpha characters, min. 10 digits • Name and email address required • Basic UX, no validation, no save • Database (tables, indexes, stored procedures) • UX with validation • Save • Help Tasks Sub Deliverables 12
  • 13.
  • 14.
    Exercise Time! –The Daily Scrum We are going to simulate a Daily Scrum. • Five volunteers to represent Team Members • One volunteer to represent a ScrumMaster 10 minutes
  • 15.
    Daily Scrum (Standup)– The Scrum Heartbeat Mar y Venk at Rog er Lynn Team Velocity Raptors Oleg Emil y Type Ready Build Verify Deployed In Progress Done In Progress Done Planned Un- Planned Y 8 A 5 G 8 U 1 W 8 M 3 H 3 B 3 E 3 N 8 Q 2 Z 3 O 5 What will you complete by the next standup?2 What did you accomplish since the last standup?1 What’s in your way, and who/how can we help?3 3Questions D 2 1. What is the team name? 2. What is the process that team is following? 3. What card or cards are blocked? 4. Who is working on a too many things? Daily Scrum
  • 16.
    Daily Scrum (Standup)Continued Mar y Venk at Rog er Lynn Team Velocity Raptors Oleg Emil y Type Ready (4) Build (6) Verify (4) Deployed In Progress Done In Progress Done Planned Un- Planned Y 8 A 5 G 8 U 1 W 8 M ★★3 ASAP H 3 B 3 D 2 E ★ 6/6 3 N 8 Q ★ 6/9 2 Z 3 ★★ ASAP O 5 ★ 6/4 1. What do the numbers 4, 6 and 4 at the top of the columns represent? 2. There is a bottleneck in this process, where is it and how do you know? 3. What are the highest priority cards and how do you know? 4. What changes in assignment could be made?
  • 17.
    A Scrum MastersReporting Tools – The Burndown 17
  • 18.
  • 19.
  • 20.
    A Scrum MastersReporting Tools – The Burnup 20
  • 21.
    A Scrum MastersReporting Tools – Cumulative Flow Diagram 21 Response Time Cycle Time Lead Time WIP
  • 22.
    Sprint Retrospective ata Glance Description • SM guides team to inspect Sprint & adapt for future: • Inspect people, relationship, process, tools, etc. • Identify “pluses” and “deltas” • Refactor approach for upcoming Sprints. Duration Half an hour to an hour Attendees ScrumMaster (leader), team, optionally Product Owner22 Outputs:  Process revisions  Project or team structure revisions  Quick hit action items  Long term improvement items  Understanding of team member perspectives A retro relies on double loop learning
  • 23.
    So what’s aScrum Master do now? 23 Planning • Coordinate all Ceremonies • Advocate for Sustainability • Ensure all voices present • Help set Structure/Cadence Day to Day • Remove blockers • Ensure WIP Limits • Enforce Sprint boundaries Retrospective • Facilitate Inspection • Track short/longer term • Process Improvements • Team Improvements Forecasting & Metrics • Report on Progress • Ensure Transparency • Communicate Trade- off decisions
  • 24.
    Upcoming Events 2016 Ourteam wants to connect with you online! Find us @LitheSpeed Interested in Agile? Become a Certified ScrumMaster Upcoming Classes with LitheSpeed President Sanjiv Augustine:  June 23-24  July 20-21  August 24-25 Stop by the LitheSpeed booth to learn more about Agile and Lean training, coaching, and consulting.
  • 25.

Editor's Notes

  • #5 Don’t shove agile at as
  • #6 https://www.youtube.com/watch?v=502ILHjX9EE
  • #7 Scrum does not proscribe “Discovery” What is the most important part of this process? What, if anything, can go wrong with this approach?