Teamwork agile way

34
TEAMWORK Jelena Barinova | @jfiodorova | bebetterleader.com AGILE WAY

description

How to form a software development team? Why I choose cross-functional feature team over functional layer team? The true story of one team.

Transcript of Teamwork agile way

Page 1: Teamwork agile way

TEAMWORK

Jelena Barinova | @jfiodorova | bebetterleader.com

AGILE WAY

Page 2: Teamwork agile way

ADFORM

Foundedin DK

YEARS

270

11

employees

Offices in 12 countries

Page 3: Teamwork agile way

ADFORM SYSTEM

Page 4: Teamwork agile way

ADFORM

DEVELOPMENT

Head of

development

Andrej

Ads

Manage-

ment

TEAM

Page 5: Teamwork agile way

How to form a team?For software product development

Page 6: Teamwork agile way

Two approaches to form a team

Functional Cross-functional

System analysts Development team

Common functional expertise Representatives from the various functions

Developers

Testers

Page 7: Teamwork agile way

Why we choose cross-functional ?

Faster feature delivery

Customer focus

Knowledge sharing

cross-functional

Page 8: Teamwork agile way

Two approaches to define scope for team

Layer ownership Feature ownership

Database

team

Backendteam

Frontend

team

Feat 1 Feat 2 Feat 3

Database

Backend

Frontend

Feat 1team

Feat 2

team

Feat 3

team

Page 9: Teamwork agile way

Why our goal - feature teams?

Increased value throughput

Autonomy

Single Point of Contact

feature

Page 10: Teamwork agile way

Two types of team members

I-shaped skills T-shaped skills

Narrow but expert knowledge Wide range of shallow & one deep skill

JavaScript JavaScriptC#.NET Puppet

Page 11: Teamwork agile way

Why I hire T-shaped people?

May cover each other

May suggest alternative solutions

T-shaped

Page 12: Teamwork agile way

Summary

Cross-functional teams

Feature oriented

T-shaped members

Page 13: Teamwork agile way

What surrounds us?In software product development

Page 14: Teamwork agile way

Two approaches to control any process

Defined Empirical

Do

CheckAct

PlanStep 1 Step 2

Step 4 Step 3

Step 5

Materials

Product

Page 15: Teamwork agile way

Which approach should be used?

Defined

EmpiricalTesla factory

Adform Kaunas

Page 16: Teamwork agile way

Two approaches for optimization

Sub-optimization System optimization

System analysts

Developers

Testers

Page 17: Teamwork agile way

Game: pass the pennies

20 coins

5 departments

5 managers (track time)

1 CEO (track time)

Page 18: Teamwork agile way

Learning points

When batch size decreases, total cycle time decreases

As total time decreases, worker time increases!

People idle more when batch size is high

Page 19: Teamwork agile way

Optimization

Sub-optimization is valid for defined process

System optimization for empirical process

Feature

request

Feature

deliveredFeature

request

Feature

delivered6 5 7 6

Total system throughput - 5 Total system throughput - 6

Page 20: Teamwork agile way

Multitasking or single-tasking

Working on several features at a time

Working on one feature at a time

Feature 1

delivered

Feat 1 Feat 2 Feat 1Feat 3 Feat 2

Feature 1

delivered

Feat 1 Feat 2Feat 1 Feat 3Feat 2

Feature 2

delivered

Feature 2

delivered

timetime

Page 21: Teamwork agile way

Game: fill-in the table

How long will it take to fill the table?

What influences speed?

Fill in form horizontally (1, I, A, 2, II, B..). Measure

time.

Fill in form vertically (1..10, I..X, A..J). Measure time.

1 I A

2 II B

3 III C

10 X J

Page 22: Teamwork agile way

Learning points

There is no multitasking, but fast switching between tasks

Time increases when switching happens

Page 23: Teamwork agile way

Multitasking in team

Complete highest priority tasks first

Work in small batches

1 completed feature is always better than 7 started

Page 24: Teamwork agile way

Summary

Empirical process:

Inspect and adopt

Single-tasking:

Focus on highest priority, work on small tasks

System optimization:

Team is able and is enabled to decide everything

Page 25: Teamwork agile way

True story of teamworkDSP team

Page 26: Teamwork agile way

Team setup

Team advocate

Product owner

UI developers

Cassandra developer

.NET developers

Page 27: Teamwork agile way

Extended team

Delivery managers

Product director

Client support

Sales

Development team

Page 28: Teamwork agile way

Feature path from idea to client

Roadmap

I Quarter

II Quarter

III Quarter

IV Quarter

Sep

tem

ber

Backlog

October

November

Oct

ob

er

October

Feature 1

Feature 2

Feature 3

Feature 4

Feature 5

Feature 6

Task board

Dev Deploy Live

Task 1Task 2

Task 3

Task 4

Task list

Task 1Task 2

Task 3

Task 4

Task 5

Feature 1

Page 29: Teamwork agile way

Meetings

Backlog review (1 hour, biweekly, team)

Standup (15 min, daily, team)

Review (1 hour, biweekly, extended team)

Retrospectves (30 min, biweekly, team)

Other meetings on demand

Page 30: Teamwork agile way

Other facts

Team in one room

3 TV screens to monitor system in a team room

6 white boards (all walls covered in whiteboards)

Personal coffee machine

Page 31: Teamwork agile way

What are your questions

Page 32: Teamwork agile way

HAPPY TEAMWORK!

Jelena Barinova | @jfiodorova | bebetterleader.com

Page 33: Teamwork agile way

Please give me

FEEDBACK!

Page 34: Teamwork agile way

SourcesPictures:Money designed by Joe Harrison from The Noun Project

Timer designed by Casey Ochinang from The Noun Project

Arrow designed by Luke Macauley from The Noun Project

Rectangle designed by Renee Ramsey-Passmore from The Noun Project

Arrow designed by Eakarius from The Noun Project

Tesla factory picture is taken from The Washington Times Communities

Idea to gather feedback:From Jurgen Appelo blog noop.nl

Games:Pass the pennies game is taken from Crisp’s blog