17
1 Team of teams slide Wrike Team of teams: How to organize effective development of big product Yuri Golikov, Sr. Director of Engineering

Yuriy Golikov, Wrike: Team of teams how to organize effective development of big product

Embed Size (px)

Citation preview

Page 1: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

1Team of teams slide Wrike

Team of teams:How to organize effective development of big product

Yuri Golikov, Sr. Director of Engineering

Page 2: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

2Team of teams slide Wrike

➔ Functional teams◆ 10+ Front-end developers◆ 15+ Back-end developers◆ 10+ QA engineers

➔ 5+ year legacy code

➔ Releasing 1 big feature per quarter

What did we have in mid 2015

Page 3: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

3Team of teams slide Wrike

➔ Speed-up featuredevelopment

➔ Provide scalability for future growth

➔ Provide transparency

Which goals did we set

Page 4: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

4Team of teams slide Wrike

➔ Divided product into scopes

➔ Organized cross-functional teams

➔ Introduced Scrum

What did we do

Page 5: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

5Team of teams slide Wrike

Recap of timing for changes

Jan 1, 2016 Feb 1, 2016 Apr 1, 2016

Decided to introduce cross-functional teams

Launch of all teams, Scrum everywhere

First big release

Mar 1, 2016

Launch of the first team, trying Scrum

Highly productive quarter

Page 6: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

6Team of teams slide Wrike

Results: what did we release in Q2 2016

Page 7: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

7Team of teams slide Wrike

Was it a battle?

Page 8: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

8Team of teams slide Wrike

No, just some difficulties

Page 9: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

9Team of teams slide Wrike

What differs from canons?

Multiple teams working on the same product

Page 10: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

10Team of teams slide Wrike

Which structure did we get

Front-End Back-End QA UX Product

Team 1

Team 2

Team 3

Team 4

Team 5

...

Team N

SCRUM TEAMS TECHNOLOGY STACK

Page 11: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

11Team of teams slide Wrike

What else differs from canons?

Big technical debt

Page 12: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

12Team of teams slide Wrike

How do we progress

Page 13: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

13Team of teams slide Wrike

➔ Yes and No

➔ No single Managers, there are Roles◆ Product Owner◆ Technical Leadership◆ People Manager

Finally, teams with no manager?

Page 14: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

14Team of teams slide Wrike

95%

Some proof

of Wrikers think that Wrike is the best company they’ve ever worked for

Page 15: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

15Team of teams slide Wrike

96%

Some proof

of Wrikers keep interested in

their responsibilities and the

product and believe that their

contribution brings value for

the product and the company

Page 16: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

16Team of teams slide Wrike

97%

Some proof

of Wrikers like the

atmosphere created

in Wrike

Page 17: Yuriy Golikov, Wrike: Team of teams  how to organize effective development of big product

17Team of teams slide Wrike

98%

Some proof

of Wrikers would

like to work at

Wrike for at least

another year