kens scrum presentation

26
What is Scrum What is Scrum Stolen from Ken Stolen from Ken Schwaber’s google video Schwaber’s google video presentation presentation

Upload: james-peckham

Post on 05-Dec-2014

1.494 views

Category:

Documents


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Kens Scrum Presentation

What is ScrumWhat is Scrum

Stolen from Ken Schwaber’s Stolen from Ken Schwaber’s google video presentation google video presentation

Page 2: Kens Scrum Presentation

scrumscrum

Not an acronymNot an acronym

RugbyRugby

Collection of best ideas from professionCollection of best ideas from profession

Page 3: Kens Scrum Presentation

Takeuchi and NonakaTakeuchi and Nonaka

StudyStudy FujiFuji ToyotaToyota 3m3m XeroxXerox

Had competitive responses to Had competitive responses to encroachment of marketshareencroachment of marketshare

Page 4: Kens Scrum Presentation

Team of very best peopleTeam of very best people

Cross functional teamCross functional team Rounded solutionRounded solution

Asked them to come up with competitive Asked them to come up with competitive responseresponse

Page 5: Kens Scrum Presentation

Smalltalk to new IDEsSmalltalk to new IDEs

Marketplace adoption of scrum came Marketplace adoption of scrum came about because of newer IDEs and about because of newer IDEs and automation of testing.automation of testing.

Page 6: Kens Scrum Presentation

XP engineering practicesXP engineering practices

Scrum as product managementScrum as product management

Xp as engineering practices that fit with Xp as engineering practices that fit with scrum to support the scrum frameworkscrum to support the scrum framework

Page 7: Kens Scrum Presentation

Scrum is not a methodologyScrum is not a methodology

Not a silver bulletNot a silver bullet

You can’t turn to the page to solve a You can’t turn to the page to solve a problemproblem

Scrum is a small framework that’s simpleScrum is a small framework that’s simple

““think of chess”think of chess”

Page 8: Kens Scrum Presentation

Agile is ‘very good’Agile is ‘very good’

With good engineers With good engineers Scrum works with anyone.Scrum works with anyone. Crap every iteration right on time! Crap every iteration right on time!

Page 9: Kens Scrum Presentation

Know where you are!Know where you are!

Sarbanes oxley borrowed transparency Sarbanes oxley borrowed transparency from scrum.from scrum.

Where are we at the end of the timebox.Where are we at the end of the timebox.

Page 10: Kens Scrum Presentation

Have something “Done”Have something “Done”

Coding standardsCoding standardsRefactoredRefactoredUnit testedUnit testedDocumentedDocumentedIntegratedIntegratedAcceptance testedAcceptance testedWhat all do you have to do at your What all do you have to do at your company to get “Potentially Shippable”company to get “Potentially Shippable”

Page 11: Kens Scrum Presentation

The bank storyThe bank story

Replacing trust systemReplacing trust system

28 legacy core feeds28 legacy core feeds

New UINew UI

Keep your job… don’t use scrum here.Keep your job… don’t use scrum here.

Page 12: Kens Scrum Presentation

Scrum framework.Scrum framework.

It’s not complex, but it is difficultIt’s not complex, but it is difficult

Page 13: Kens Scrum Presentation

And a few rulesAnd a few rules

Inspect or adapt loop (empirical)Inspect or adapt loop (empirical)

Every day “make transparent where you Every day “make transparent where you are”are”

““Done”Done”

Page 14: Kens Scrum Presentation

““News!”News!”

Burn downBurn down

Page 15: Kens Scrum Presentation

Single wringable neck!Single wringable neck!

Person makes decisions for every single Person makes decisions for every single release.release.

Comparing where they are to where they Comparing where they are to where they want to bewant to be

Makes decisions!Makes decisions!

Accountability to the sponsorAccountability to the sponsor

Page 16: Kens Scrum Presentation

The news problemThe news problem

Are you going to do something about it?Are you going to do something about it?

Page 17: Kens Scrum Presentation

Time-honored traditionsTime-honored traditions

Plaster code in without refactoringPlaster code in without refactoring

Skip unit testsSkip unit tests

Skip acceptance testsSkip acceptance tests

Work long hours!Work long hours!

Page 18: Kens Scrum Presentation

High moon studiosHigh moon studios

Sammy sega was the original ownerSammy sega was the original owner Use scrumUse scrum Sustainable paceSustainable pace

Japan says 12-14 hour days!Japan says 12-14 hour days! 60% increase in defects60% increase in defects Cost more than offset functionalityCost more than offset functionality

Page 19: Kens Scrum Presentation

Core software ‘problem’Core software ‘problem’

Our velocity 24Our velocity 24

Core velocity 10Core velocity 10

Multiple dev teams for new functionalityMultiple dev teams for new functionality

Page 20: Kens Scrum Presentation

Common thingsCommon things

FragileFragile

No automated testsNo automated tests

Few ‘suckers’ left to work on itFew ‘suckers’ left to work on it

Page 21: Kens Scrum Presentation

PRDs & MRDsPRDs & MRDs

65% of functionality maintained and 65% of functionality maintained and sustained is rarely used.sustained is rarely used.

Page 22: Kens Scrum Presentation

PRDs changingPRDs changing

Stand owner up against the wall….Stand owner up against the wall….

We’ve forced them to not only spit out a We’ve forced them to not only spit out a bunch of feature with little or no value, but bunch of feature with little or no value, but also ‘fearful’ of changing our minds.also ‘fearful’ of changing our minds.

Page 23: Kens Scrum Presentation

Scrum masterScrum master

Aka “the prick“Aka “the prick“

Makes sure you don’t cut qualityMakes sure you don’t cut quality

No authorityNo authority

If we’ve defined “Done” to be demo-able If we’ve defined “Done” to be demo-able their job is to make sure it’s there.their job is to make sure it’s there.

Page 24: Kens Scrum Presentation

Hopeless professional areasHopeless professional areas

Use to doing incredible things with no Use to doing incredible things with no respect, no authority, and no hope that it respect, no authority, and no hope that it will ever get done.will ever get done.

Page 25: Kens Scrum Presentation

Non-functional requirementsNon-functional requirements

ArchitecturalArchitectural

DesignDesign

Deliver ‘something’ demonstrable.Deliver ‘something’ demonstrable.

Page 26: Kens Scrum Presentation

Scrum failed! Why?Scrum failed! Why?

Put the framework in placePut the framework in place

Try to understand the problems that are being Try to understand the problems that are being uncovered were already there!uncovered were already there! Unwillingness for the company to let engineers do Unwillingness for the company to let engineers do

their job (self direction)their job (self direction) Unwillingness of engineers to improve engineering Unwillingness of engineers to improve engineering

practicespractices Unwillingness or inability for engineers to deliver Unwillingness or inability for engineers to deliver

‘potentially shippable’ code every iteration‘potentially shippable’ code every iteration

Dedication to software and engineering.Dedication to software and engineering.