Scrum Training Jibes 11-11-15

Scrum
Training
Jibes
11 November 2015
Barend van der Plas
Introduc1on
Who are you?
-‐  What is your role?
-‐  How long at Jibes?
-‐  What is your experience with Scrum?
-‐  What are your goals and/or expectaEons?

11-‐11-‐15 barend.van.der.plas@gmail.com 2
Goals of the training
•  Learn Agile principles
•  Learn/refresh Scrum basics
•  Have Fun!
Warming-‐up
Agile teams do very liOle planning
Agile is not suited for fixed price projects
Agile is only suitable for co-‐located teams
Agile teams don’t create documentaEon
The Marshmellow challenge
Goal
•  Build highest free-‐standing structure
Rules
•  Teams of 4-‐5
•  Only use materials in your kit
•  En3re marshmellow on top!
•  No holding on to structure when measured
•  Measured from surface table to top of marshmellow
•  Max 18 minutes
QuesEons? START!
Marshmellow takeaways
Protoyping maOers
-‐  Review to improve
-‐  Test your assumpEons
-‐  Fail fast, fail oên, learn fast
Diverse skills maOer

Self organize / Work as one team
Why Agile?
3 things we wish were true
-‐  Customer knows what he wants
-‐  Developers know how to build it
-‐  Nothing will change along the way
3 things we have to live with

-‐  Customer discovers what he wants
-‐  Developers discover how to build it
-‐  Many things change along the way
Agile is about controlling complexity
Agile principles
Our$highest$priority$is$to$satisfy$$the$ The$most$efficient$and$effective$
Continuous$attention$to$technical$
customer$through$early$and$ method$of$conveying$information$to$
excellence$and$good$design$
continuous$delivery$of$valuable$ and$within$a$development$team$is$
enhances$agility
software face;to;face$conversation
Agile$processes$promote$sustainable$
Deliver$working$software$frequently,$
The$best$architectures,$requirements$ development.$The$sponsors,$
from$a$couple$of$weeks$to$a$couple$
and$designs$emerge$from$self; developers$and$users$should$be$able$
of$months,$with$a$preference$for$the$
organizing$teams to$maintain$a$constant$pace$
shorter$timescale
indefinitely
Build$projects$around$motivated$ Welcome$changing$requirements,$
Simplicity$– the$art$of$maximizing$the$
individuals.$Give$them$the$ even$late$in$development.$Agile$
amount$of$work$not$done$– is$
environment$and$support$they$need,$ processes$harness$change$for$the$
essential
and$trust$them$to$get$the$job$done. customer’s$competitive$advantage
At$regular$intervals,$the$team$reflects$
Business$people$and$developers$
Working$software$is$the$primary$ on$how$to$become$more$effective,$
must$work$together$daily$throughout$
measure$of$progress then$tunes$and$adjusts$its$behavior$
the$project
accordingly
The Agile Clock
Goal
•  Each team needs to express the essence of each Agile principle in three words or less

Rules
•  Words should be wriOen on sEckers and hung within the circle on a flip chart.
•  Thus, we create the clock
•  Each number on the clock corresponds to a specific principle of the Agile Manifesto
•  The higher the number, the more the principle reflects your daily pracEce
•  Visualize each principle by drawing an icon
•  Max 20 minutes

QuesEons? START!
Agility is working in Itera1ons:
Deliver Early & OJen
Plan Analyze Design Code Test Release
Itera1ve vs incremental
Incremental
IteraEve
Tradi1onal vs Agile development
Tradi1onal vs Agile development
barend.van.der.plas@gmail.com
What is Scrum?
•  Framework for complex product development
•  Not only for managing software development
•  Suitable for managing many types of work
–  complex environment
–  creaEve team-‐work
The new new product development game,

Takeuchi and Nonaka, 1986
As one Team,
Multi disciplinary, SCRUM!

Dedicated and focused,
Working towards a clear goal
Where highest business value gets highest priority
Under continuous improvement (kaizen)
Continuously delivering working solutions

Total Scrum Process
SCRUM MASTER
PRODUCT OWNER
TEAM
Facilitates
the scrum
process
SCRUM MASTER Ensures that the

team becomes
self-‐organizing
Removes
impediments
Has a product vision
and defines the
business goal(s)
Determines the
business value
PRODUCT OWNER
Prioritizes the Manages the

backlog Stakeholders
Work on
User stories
Es3mate
User
stories
Self
organizing
TEAM
Total Scrum Process
The essence
•  Transparancy
•  Inspect
•  Adapt
Product Backlog
Product Backlog
•  Backbone of the project

•  Everything that needs to be done
•  Always prioritized on business value
•  Maintained by product owner
•  Estimated by the team
•  The lower on the backlog,..
…the less detailed!
Case
Organise a Christmass Dinner with friends

What needs to be done to arrange this?

Brainstorm a list of acEons in 5 minutes
Priori1ze
Prioritize the actions / elements of the case in
order of importance (value) in 10 minutes
What acEon you really need to start with?

Which acEons can you skip?
Which acEons can be split in more important en
less important acEons (and sorted)
User stories
As a… <user>
I want to … <goal>
So that …. <value>
Sprint planning
Sprint Planning
•  User Stories with highest business value first

•  Discussed in detail with the team
•  EsEmate with team the work for 1-‐4 weeks
•  Break-‐down of stories into tasks (1-‐8 hrs)
•  To do’s prioriEzed on the Scrum board
Defini1on of Done
•  Story complete
–  AcceptaEon criteria (!)
•  Code complete
–  Code review / pair programming
–  Unit test
–  IntegraEon test
•  Accepted by the Product Owner
= PotenEally releasable So^ware !
Planning Poker
Planning Poker
Ready for Sprint?
INVEST criteria
•  Immediately acEonable & Independent

•  NegoEable
•  Valuable
•  Estimable
•  Sizable
•  Testable
Sprint
Sprint
•  Team member picks up the first to do on scrum board
•  Write name on it and put it “in progress”
•  If finished to do moves to ‘done’
•  PO accepts done stories and rejects stories not done
•  Everything on done = sprint done!
•  End of the sprint = determine velocity
•  No changes or interrupEons during the sprint
•  PO prepares next sprint during the current one
Daily Standup
Daily Standup
1.  What did I achieve yesterday?
2.  What will I achieve today?
3.  What is holding me back (impediments)?

Do I need help?
Sprint Review
and Retrospec1ve
Sprint Review
•  Review/demo this sprint’s working software
•  Entire team + stakeholders
•  Collect feedback
•  Check product vision / alignment

Retrospec1ve
•  After the sprint review follows the retrospective:
•  What went well?

•  What could we have done better?
•  How?
= To do / Improvements for next sprint
Sprint 2, Sprint 3 , etc
Summary
•  Highest business value first (prioriEze and focus)
•  Act quickly on change (planning per sprint)
•  Constant delivery of a working soluEon
•  Short feedback loop (sprint review)
•  ConEnuous improvement (retro)
•  Transparency and communicaEon (standup, demo, retro)
•  Team spirit (dedicated, 1 goal)
Wrap-‐up
•  Takeaways for today
•  Homework (18-‐11-‐15)
•  Watch video Lyssa Adkins – The Scrum Framework
•  Prepare backlog for your project/assignment
•  Happiness metric

Scrum Training Jibes 11-11-15

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Scrum Training Jibes 11-11-15

Uploaded by

Copyright:

Available Formats

Scrum

Diverse skills maOer

3 things we have to live with

Plan Analyze Design Code Test Release

The new new product development game,

Multi disciplinary, SCRUM!

Working towards a clear goal

Where highest business value gets highest priority

Under continuous improvement (kaizen)

Continuously delivering working solutions

SCRUM MASTER Ensures that the

Prioritizes the Manages the

• Backbone of the project

Organise a Christmass Dinner with friends

What acEon you really need to start with?

I want to … <goal>

So that …. <value>

• User Stories with highest business value ﬁrst

= PotenEally releasable So^ware !

• Immediately acEonable & Independent

• PO prepares next sprint during the current one

1. What did I achieve yesterday?

2. What will I achieve today?

3. What is holding me back (impediments)?

• Review/demo this sprint’s working software

• Entire team + stakeholders

• Check product vision / alignment

• After the sprint review follows the retrospective:

• What went well?

You might also like

•  Backbone of the project

•  User Stories with highest business value ﬁrst

•  Immediately acEonable & Independent

•  PO prepares next sprint during the current one

1.  What did I achieve yesterday?

2.  What will I achieve today?

3.  What is holding me back (impediments)?

•  Review/demo this sprint’s working software

•  Entire team + stakeholders

•  Check product vision / alignment

•  After the sprint review follows the retrospective:

•  What went well?