scrum by the book | maciej gudan | ltg-17

“Scrum by the book” Building a lean organization and introducing Scrum to an intensive industry during the fast company growth, Maciej Gudan, 05.11.2013

Agenda •  Show that the environment is not necessarily the

simplest one •  Present our lean vision •  Highlight example challenges •  Share few things which worked for us •  How far we have gone

How complex can it be?

•  eGaming industry •  Millions of users •  Thousands bets per minutes •  Huge pressure •  Very fast users reaction •  Time to market •  Hierarchical structures •  Growing extremely fast

How complex can it be?

How complex can it be?

How complex can it be?

How complex can it be?

How complex can it be?

How complex can it be?

How complex can it be?

How complex can it be?

How complex can it be?

How complex can it be?

And the company is still growing!

Define what matters •  Time to market •  Reliability •  Scalability •  Growth support •  Visibility •  Control •  Maintain great spirit and energy

Java

PO

SM

PM

BA

QA

5-7 SWE

HTML QA

JAVA

Product Backlog Fixed iterations

Scrum by the book!

POM SMM

SWETM or JavaTM?

You know, we have an exceptional situation here... •  ~30 people •  Time to market is extremely crucial •  Very positive and energizing •  We don’t have prior Agile experience •  Here we have backend, frontend, tester •  We work with up to 200 pages specification •  We have almost daily priority changes •  We have huge number of requests •  We are growing very fast

People like Scrum, right? •  “Which book?” •  “I don’t like HTML” •  “I like where I sit” •  “I can’t estimate without detail analysis” •  “We can’t provide you Stories, we work with Specifications” •  “In Agile you have to adapt, we want a mix of Waterfall and Agile. We want

no preparations, frequent changes but fixed scope, time and quality!” •  “Kanban fits better!”

This required serious attention!

Try this •  Set a vision, a common base and practice it •  Teamwork/Involve people/build relations •  Look at the system •  Communicate, listen, communicate, listen, com... •  Accept that changes takes time •  Scrum Masters are crucial •  5 Why •  ALWAYS THINK HOW!

How far have we gone? •  From 30 to 100 people •  Scalability •  Release cycles from 3 months to 1 - 4 weeks •  From 100 p. specs to Stories with Acceptance Criterias •  From FE/BE/QA/Native to SWE •  From plenty of misunderstandings to almost none •  Collocated, fixed Teams •  PO, SM Teams •  etc.

Thank you!

maciej.gudan@gmail.com Images taken from the following sources: http://mksdesignss.com/wp-content/uploads/2012/06/never_give_up_Ssz7U_640_285-300x357.jpg

http://media2.s-nbcnews.com/j/streams/2013/February/130221/1C6110135-tdy-130221-scaredbaby-1.blocks_desktop_tease.jpg

http://www.collegesocialmagazine.com/wp-content/uploads/2013/06/scared.jpg