Scrum Workshop - September 2013

7/27/2019 Scrum Workshop - September 2013

1/44

Scrum

Nothing endures but change (Heraclitus)

Tuesday, 1 October 13


2/44

Why do we do Scrum? No, seriously, why?



3/44

Standup and close your eyes



4/44

Standup and close your eyes

Delivered late on several occasions

Disappointed to your customers

Spent over the budget

Received changing requirements

Experienced team changes

Developed features that nobody uses

...



5/44

What were we using

in the past?

Waterfall

Its great strength is that it is

supremely logical: think before

you build, write it all down, follow

a plan, and keep everything asorganized as possible.



6/44

Waterfalls weakness



7/44

Waterfalls weakness Humans are not machines



8/44Tuesday, 1 October 13


9/44

What is Scrum?



10/44

Inspect and Adapt Endless cycle

DirectExperience

Frequent

Inspection

Adjustment& Adaptation



12/44

Scrum values

Focus

Visibility

Respect

Commitment

Courage



13/44

Focus activity

1

23

...

26

a

bc

...

z

I

IIIII

...

XXVI

Goal

Time: 2 min

Group A:

Columns:- 1, 2, 3... 26

- a, b, c... z

- I, II, III... XXVI

Group B:

Rows:- 1, a, I

- 2, b, II

- ...

- 26, z, XXVI

Two groups

Raise your hand when you finish!



15/44

Who is whoScrum Roles



16/44

Product OwnerOwner of the project vision

Represents the customer



17/44

Product OwnerOwner of the project vision

Represents the customer

Define features (according to vision)

Prioritize features (according to ROI)

Pick release dates

Give feedback

Manage stakeholders

Accept or reject results



18/44

The TeamSmall (59 people)

Colocated - Cross-functional

Self-organized - Full-time



19/44

The TeamSmall (59 people)

Colocated - Cross-functional

Self-organized - Full-time

Define tasks

Estimate effort

Develop product

Ensure quality

Evolve processes



20/44

Scrum MasterServant leader, team protector,

troubleshooter, Scrum guide...



21/44

Scrum MasterServant leader, team protector,

troubleshooter, Scrum guide...

Remove impediments

Prevent interruptions

Facilitate the teamSupport the process

Manage management



22/44

Lets scrum it!

4 Teams

1 Product Owner

3 Team members

Goal:Try to reproduce a drawing



23/44

C&D

can:

- Write as much as they want

cant:

- Speak- Touch

- Point

- Draw

A&B

can:

- Speak as much as they wantcant:

- Write

- Touch

- Point

- Draw



24/44

ACCUMULATOR

SOLARCOLLECTOR

PrimaryCircuit

Auxiliary

Energy

SecondaryCircuit

ACS



25/44

Retrospective & Conclusions



26/44

Scrum artifacts



27/44

User Story Product Backlog Item...

As a user

I want something

so that benefit

As a who

I want whatso that why



28/44

User Story Product Backlog Item...

As a user

I want something

so that benefit

As a who

I want whatso that why

where is the how?



29/44

INVEST

Independent The user story should be self-contained,

in a way that there is no inherent

dependency on another user story

Negotiable User stories, up until they are part of an iteration, can

always be changed and rewritten

Valuable A user story must deliver value to the end

user

Estimable You must always be able to estimate the

size of a user story

Sized appropriately or Small User stories should not be so big as to

become impossible to plan/task/prioritize

with a certain level of certainty

Testable The user story or its related description

must provide the necessary information

to make test development possible



30/44

Product Backlog



31/44

Sprint backlog



32/44

Definition of Done DONE DONE



33/44

Burndown chart Are we doing well?



34/44

Scrum meetings



35/44

Sprint planningteam capacity + product

backlog + current product +

business + technologies =

GOAL



36/44

Daily ScrumCommitment and accountability

Say what you do, do what you say

Whole world is invited



37/44

Sprint reviewSatisfy Product Owner

Get feedback on product



38/44

Sprint retrospectiveEvolve the process

Reflect on process and product

Whole team participates



39/44

The airplane factory



40/44

Basic description

Teams with 4-7 people (each

team will represent a factory)

We will build paper airplanes

Iterations and re-planning of 2

minutes each

Unconditional respect of time!

Estimation before each sprint



41/44

Rules

One fold per person and pass it

on

Must be a plane (wings)

Must have a blunt tip

Must have 6 windows

Must fly 3 meters

1/4 piece A4 paper per plane

Test only on test strip

Only tested/passed planescount

WIP must be discarded at the

end of the sprint



42/44

Retrospective

Did you get what the client

wanted in the beginning?

Would a prototype have

helped?

Did the estimates get better aswe better understand the

requirements?

Was the concept of inspect/

adapt useful?

Was it useful to removeimpediments?

And changing the scope?



43/44

Q & A



44/44

References

Beck et al.Agile manifesto. http://agilemanifesto.org/

Cohn. Succeeding with Agile. http://www.succeedingwithagile.com/

Schwaber & Sutherland. Scrum Guide. https://www.scrum.org/Scrum-Guides

Appelo. The Zen of Scrum. http://www.slideshare.net/jurgenappelo/the-zen-

of-scrum-10

Buenosvinos. Scrum al detalle. http://www.slideshare.net/carlosbuenosvinos/

scrum-al-detalle-revision-prctica-y-perversiones-humanas

Benefield & Deemer. Scrum Primer. http://scrumprimer.org/

Yip. Its not just standing up. http://martinfowler.com/articles/itsNotJustStandingUp.html

Dupuy. The Short Short Story. http://www.scrumalliance.org/community/

articles/2011/2011-june/the-short-short-story
http://www.scrumalliance.org/community/articles/2011/2011-june/the-short-short-storyhttp://www.scrumalliance.org/community/articles/2011/2011-june/the-short-short-storyhttp://www.scrumalliance.org/community/articles/2011/2011-june/the-short-short-storyhttp://www.scrumalliance.org/community/articles/2011/2011-june/the-short-short-storyhttp://martinfowler.com/articles/itsNotJustStandingUp.htmlhttp://martinfowler.com/articles/itsNotJustStandingUp.htmlhttp://scrumprimer.org/http://www.slideshare.net/carlosbuenosvinos/scrum-al-detalle-revision-prctica-y-perversiones-humanashttp://www.slideshare.net/carlosbuenosvinos/scrum-al-detalle-revision-prctica-y-perversiones-humanashttp://www.slideshare.net/carlosbuenosvinos/scrum-al-detalle-revision-prctica-y-perversiones-humanashttp://www.slideshare.net/carlosbuenosvinos/scrum-al-detalle-revision-prctica-y-perversiones-humanashttp://www.slideshare.net/jurgenappelo/the-zen-of-scrum-10http://www.slideshare.net/jurgenappelo/the-zen-of-scrum-10https://www.scrum.org/Scrum-Guideshttp://www.scrumalliance.org/community/articles/2011/2011-june/the-short-short-storyhttp://www.scrumalliance.org/community/articles/2011/2011-june/the-short-short-storyhttp://www.scrumalliance.org/community/articles/2011/2011-june/the-short-short-storyhttp://www.scrumalliance.org/community/articles/2011/2011-june/the-short-short-storyhttp://martinfowler.com/articles/itsNotJustStandingUp.htmlhttp://martinfowler.com/articles/itsNotJustStandingUp.htmlhttp://martinfowler.com/articles/itsNotJustStandingUp.htmlhttp://martinfowler.com/articles/itsNotJustStandingUp.htmlhttp://scrumprimer.org/http://scrumprimer.org/http://www.slideshare.net/carlosbuenosvinos/scrum-al-detalle-revision-prctica-y-perversiones-humanashttp://www.slideshare.net/carlosbuenosvinos/scrum-al-detalle-revision-prctica-y-perversiones-humanashttp://www.slideshare.net/carlosbuenosvinos/scrum-al-detalle-revision-prctica-y-perversiones-humanashttp://www.slideshare.net/carlosbuenosvinos/scrum-al-detalle-revision-prctica-y-perversiones-humanashttp://www.slideshare.net/jurgenappelo/the-zen-of-scrum-10http://www.slideshare.net/jurgenappelo/the-zen-of-scrum-10http://www.slideshare.net/jurgenappelo/the-zen-of-scrum-10http://www.slideshare.net/jurgenappelo/the-zen-of-scrum-10https://www.scrum.org/Scrum-Guideshttps://www.scrum.org/Scrum-Guideshttp://www.succeedingwithagile.com/http://www.succeedingwithagile.com/http://agilemanifesto.org/http://agilemanifesto.org/

Scrum Workshop - September 2013

Documents

Transcript of Scrum Workshop - September 2013