Why Scrum?Kane MarCertified Scrum Coach and Trainer.

http://KaneMar.comhttp://Scrumology.com.au

Creative Commons Attribution 3.0

Kane Mar and Others (see credits)

You are free:

to Share — to copy, distribute and transmit the work

to Remix — to adapt the work

Under the following conditions:

Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work)

http://creativecommons.org/licenses/by/3.0/

Agenda

A quick review of what is Scrum

Why Scrum?

How is this possible?

The trends in adopting Scrum ...3, 2, 1.

About Me.

A quick review of Scrum

“The New New Product Development Game,” by Hirotaka Takeuchi, Ikujiro Nonaka. Havard Business Review, Jan 1, 1986.

Fuji-Xerox, Canon, Honda, NEC, Epson,Brother, 3M, Xerox, and HP.

References the sport of Rugby

A quick review of Scrum

“Scrum Development Process,” Ken Schwaber and Jeff Sutherland, OOPSLA 1995

“Agile Software Development with Scrum,” Ken Schwaber and Mike Beedle, 2001

“Agile Project Management with Scrum,” Ken Schwaber

“Scrum and the Enterprise,” Ken Schwaber

What is Scrum?

What is Scrum?

What is Scrum?

What is Scrum?

Why Scrum?

Scrum is the most efficient way of going from an idea to high quality code in production, that I know of

Scrum teams can push code into a production every two weeks (although they don’t have to)

How is this possible?

How can a team build a complete functional application in two weeks?

What if the architectural framework takes two months to build?

What about the quality of the code?

How can a team build an app. in two weeks?

They cannot ...

However they can build some functional slice of the application, and

They can build the highest priority piece of functionality

How can a team build an app. in two weeks?

Sushi Slices

Each slices is part of the complete whole

Each slice can stand on it’s own

This equates to slices of functionality in software

How is this possible?

How can a team build a complete functional application in two weeks?

What if the architectural framework takes two months to build?

What about the quality of the code?

What if it takes two months?

60% of functions are never used,

So, why not deliver the 40% that will be used and build the rest when we need it?

Only build what you need right now

How is this possible?

How can a team build a complete functional application in two weeks?

What if the architectural framework takes 2 months to build?

What about the quality of the code?

What about the quality of the code?

Agile Engineering practices are necessary in order to achieve this

Continuous Integration, TDD and (now) Continuous Deployment

What about the quality of the code?

“Software is an organizational asset and decisions to cut quality must be made by executive management and reflected in the financial statements.”

“Canary in the Coal Mine,” Ken Schwaber http://www.infoq.com/presentations/agile-quality-canary-coalmine

Trends in adopting Scrum

The adoption of Scrum has changed over the years as Scrum has become more mainstream

Once the domain of risk takers and early adopters, Scrum is now being adopted by a different group of people with different motivations

Reason #3

“At risk” projects

They frequently have nothing left to lose

Desperate teams will try anything

Reason #2

Not meeting market demand

Does it take 4 months to get and approvel PRD?

Do you write more documentation than software?

Reason #1

Your competitors are using Scrum

If you’re competitors are using Scrum, it’s not a level playing field ... they’re playing a different game.

Summary

Why Scrum?

Because it’s the most efficient way to go from concept to high quality code in production

Scrum changes the business of software

Credits

http://www.flickr.com/photos/rugby_pioneers/

http://www.flickr.com/photos/66164549@N00/

http://www.flicker.com/photos/vernhart/

http://commons.wikimedia.org/wiki/Lewis_Hine

http://www.flickr.com/photos/samuraislice/

http://www.flickr.com/photos/giovannijl-s_photohut/

References

“Scrum is hard and disruptive”, Ken Schwaber 2006

“Agile Software Development with Scrum,” Ken Schwaber and Mike Beedle, 2001

“Agile Project Management with Scrum”, Ken Schwaber

“Scrum and the Enterprise”, Ken Schwaber

“Scrum in 5 minutes”, Softhouse Nordic AB http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf