Agile in Skroutz?by Giorgos Tsiftsis

history● waterfall ● agile manifesto ● agile methodologies (scrum, xp …)● meanwhile in Japan: kanban, lean production ● what were the problems?

○ limited resources ○ more experimentations○ embrace changes

agileadjective

1. quick and well-coordinated in movement; “an agile leap”.2. active; lively: “an agile person”.3. marked by an ability to think quickly; mentally acute or aware: “She's 95

and still very agile.”

coordinationnoun

1. the act or state of coordinating or of being coordinated.2. proper order or relationship.3. harmonious combination or interaction, as of functions or parts.

my definition of ‘agile’1. Do small & quick steps 2. Connect all feedback loops 3. Learn from mistakes

skroutz● complicated product

○ ~3.000 customers ○ 500.000 users / day○ 3 countries

● big codebase ○ ~800 commits / month○ ~50 engineers ○ ~15 teams ○ 5 segments

● we do not do scrum :)

skroutz : the good parts

Problem observed at 9:35

Problem solved at 9:52

skroutz : the good parts

● More than 60 boards● Discussions in cards ● Ideas / Bugs / Proposals

skroutz : the good parts

● Happy dev dedicated board● Kanban● Rotate every week

skroutz : the good parts

● Internal app● Knowledge base● Accessible for all

skroutz : the good parts

102 design documents

solutions● Code Reviews● 15+ deploys per day● Extensive monitoring● Tests ● A/B tests● Usability tests● Discussions ● Design documents● Internal wikis (github / phabricator)

skroutz : the bad parts ● Lack of Fail Fast mechanisms● No structured retros ● Codebase attachment ● Little product ownership● Poor planning in some cases

that’s all!any questions?