70

When scrum goes bad

Embed Size (px)

Citation preview

Page 1: When scrum goes bad
Page 2: When scrum goes bad

When Scrum goes bador does it?

Jesse HouwingLead Consultant Xpirit@jessehouwing

#TECHDAYSNL #PROSCRUMDEV

Jesse HouwingLead Consultant Xpirit@jessehouwing

Page 3: When scrum goes bad

JesseHouwingScrum trainer at Xpirit@[email protected]

Page 4: When scrum goes bad

Why are you here?

Page 5: When scrum goes bad

I believe in Scrum

Page 6: When scrum goes bad
Page 7: When scrum goes bad

Scrum says… ?

Page 8: When scrum goes bad

So when does Scrum go bad?Or when is Scrum bad?

Page 9: When scrum goes bad

Velocity your primary measure of progress?

Page 10: When scrum goes bad

Looking good at a glance?

Page 11: When scrum goes bad

Direction is needed

Page 12: When scrum goes bad

If you measure anything

Measure happiness

Page 13: When scrum goes bad

So what does Scrum say?

Page 14: When scrum goes bad

My tool is better than yours

Page 15: When scrum goes bad

So what does Scrum say?It encourages you to use what works for you…

Page 16: When scrum goes bad

Working software and #NoDocumentation?

Page 17: When scrum goes bad

Because, come on who reads all this stuff?

Page 18: When scrum goes bad

Ever tried assembling Lego or Ikea without a manual?

Page 19: When scrum goes bad

Executable Specifications…

Page 20: When scrum goes bad

So what does Scrum say?

Page 21: When scrum goes bad

Approve or blame?

Page 22: When scrum goes bad

git push origin -f

Page 23: When scrum goes bad

So what does Scrum say?

Continuous Delivery!and of course integration

Page 24: When scrum goes bad

So what does Scrum say?Only show accepted work, in a releasable state.

Page 25: When scrum goes bad

Cross functional individualEveryone can do everything

Page 26: When scrum goes bad

Cross functional teamThe team has every skill in order to reach

its goal

Page 27: When scrum goes bad

Call them I shaped,

T Shaped or E Shaped

Page 28: When scrum goes bad

ProgrammingArchitecture

Testing UX

Page 29: When scrum goes bad

So what does Scrum say?The team must have all the skills to create a product increment

Page 30: When scrum goes bad

Commitment

Page 31: When scrum goes bad

Forecast

Page 32: When scrum goes bad

What does Scrum say?people commit to achieving the goals of the Scrum Team

Page 33: When scrum goes bad

Too many meetingNot enough time…C

Page 34: When scrum goes bad

% spent in meetings?

Page 35: When scrum goes bad

A maximum of 25%

Page 36: When scrum goes bad

160 hours in a sprint8 hours sprint planning7 hours review and retro20 x 0.25 = 5 hours daily scrum10% * (160-8-7-5) = 14 hours refinement

34 hours in eventsAbout a day per week

Page 37: When scrum goes bad

What other meetings do you attend to?

Page 38: When scrum goes bad

Are your reviews effective?

Page 39: When scrum goes bad

What does scrum say?minimize the need for meeting not defined in Scrumend whenever the purpose of the event is achieveddo not allow waste in the process

Page 40: When scrum goes bad

How much time was spent om planning, functional design, technical design and testing before?

Page 41: When scrum goes bad

DoneDone Done! Done Done Done! London?

Page 42: When scrum goes bad

Sometimes manifested as:The perpetual MVP

Page 43: When scrum goes bad

Or manifested as:The twinkling pixel…

Page 44: When scrum goes bad

So what does Scrum say?everyone must understand what “Done” meansa product owner may choose to immediately release the increment

Page 45: When scrum goes bad

Definition of ReadyYet another stage gate?

Page 46: When scrum goes bad

Up to specs?

Page 47: When scrum goes bad

So what does Scrum say?Items that can be “Done” by the development team within one sprint are deemed “Ready”

Page 48: When scrum goes bad

To support more teams?That includes all the Orcs and Goblins

Page 49: When scrum goes bad

One PO to rule them allThat includes all the Orcs and Goblins

Page 50: When scrum goes bad

So what does Scrum say?Product Owner is the sole person responsible for managing the Product Backlogthe Product Owner is one person, not a committee, but may represent onethe entire organization must respect his or her decisions.

Page 51: When scrum goes bad

Speed VS Agility

Page 52: When scrum goes bad

So what does Scrum say?Not much. Except to be ready and to embrace change when needed

Page 53: When scrum goes bad

Dealing with unplanned work

Page 54: When scrum goes bad

So what does Scrum say?All work comes in through the Product Backlog (though some work faster than others)Ideally no work interrupts the sprint. If it does the team should inspect and adapt to prevent reoccurrence

Page 55: When scrum goes bad

The most prickly oneReally large scrum teams or multiple scrum teams

Page 56: When scrum goes bad

It only adds more confusion

Page 57: When scrum goes bad

As products / projects / releases scaleTeams, the way they work and the product

change

Page 58: When scrum goes bad

Architecture changes

Page 59: When scrum goes bad

The two pizza teamor was it the two team pizza

Page 60: When scrum goes bad

You’ll need to formalizeIt can’t be one big party

Page 61: When scrum goes bad

So what does Scrum say?The optimal Development Team size is small enough to remain nimble

Yet large enough to complete significant work.Large teams generate too much complexity for an empirical process to manage

Page 62: When scrum goes bad

Scaling is hardLots of good practices, but you need to make it work

for you

Page 63: When scrum goes bad

Is Scrum the ultimate Process Compressor?

Page 64: When scrum goes bad

So what does Scrum say?Not much… Only to use empiricism to improve

Page 65: When scrum goes bad

It gives you a mirror

Page 66: When scrum goes bad

And by working hard to improve

Page 67: When scrum goes bad

You may come to like what you see

Page 68: When scrum goes bad

Next steps…Stay calm and Scrum on.

Page 69: When scrum goes bad

JesseHouwingScrum trainer at Xpirit@[email protected]

Page 70: When scrum goes bad

THANK YOU!Jesse HouwingLead Consultant Xpirit

[email protected]@jessehouwing

#TECHDAYSNL #PROSCRUMDEV

bit.ly/XpiritMagazineJesse HouwingLead Consultant Xpirit

[email protected]@jessehouwing