75
Effective Teams Pawel Brodzinski @pawelbrodzinski

Effective Teams

Embed Size (px)

DESCRIPTION

What pictures do we have in our minds when we think about effective software development? Code quality, continuous integration, pair programming or what have you. While I’m a big fan of all of them I would challenge the concept that this is the only, or the most important, area which developers should focus on. Building software is a collective effort of people working in different roles and this should always be a starting point to a discussion about effectiveness. The missing piece may be software craftsmanship but it may also be handful of dull chores that few would fancy doing. How can we tell? What should we use as guidance? And, at the end of the day, how to build software effectively?

Citation preview

Page 1: Effective Teams

Effective Teams

Pawel Brodzinski

@pawelbrodzinski

Page 2: Effective Teams

Hi, I’m Pawel

Lunar Logic http://lunarlogic.io

Blog http://brodzinski.com

Twitter @pawelbrodzinski

Page 3: Effective Teams

Teamwork

Page 4: Effective Teams

Teamwork

Page 5: Effective Teams

IE7 fixes, anyone?

Page 6: Effective Teams

Functional testing, anyone?

Page 7: Effective Teams
Page 8: Effective Teams

There always is a bottleneck

Page 9: Effective Teams
Page 10: Effective Teams

Visualization helps to

understand work and spot problems

Page 11: Effective Teams

What’s the problem with queues again?

Page 12: Effective Teams

Source: Gerald Weinberg, Quality Software Management: Vol. 1 System Thinking

Cost of multitasking

Page 13: Effective Teams

Zeigarnik Effect

Tendency to experience intrusive thought about an objective left incomplete

Source: S. Greist-Bousquet, N. Shiffman: The effect of task interruption and closure on perceived duration

Page 14: Effective Teams

Cost of task switching

is rooted in interference

from thoughts about the task

you are not doing

Eyal Ophir

Page 15: Effective Teams

Source: E. Ophir, C. Nass, A. Wagner: Cognitive control in media multitaskers

Multitasking cripples quality

Page 16: Effective Teams

Teams that worked

only on a single project

were significantly better in

terms of defects density

Larry Maccherone

Page 17: Effective Teams

Work in Progress limits

5O

Page 18: Effective Teams
Page 19: Effective Teams
Page 20: Effective Teams

WIP limits result in slack time

Page 21: Effective Teams

Helping others

Page 22: Effective Teams

Do you remember

your answers?

Page 23: Effective Teams

Impact of WIP limits

5O

Page 24: Effective Teams

Paying technical debt back, anyone?

Page 25: Effective Teams

Slack time incentivizes system improvements

Page 26: Effective Teams

Into the trenches

Page 27: Effective Teams
Page 28: Effective Teams

Why do features you

build work this specific way?

Page 29: Effective Teams

Why do clients want these features?

Page 30: Effective Teams

What is (roughly) value of the features?

Page 31: Effective Teams

Would you speak up if

a feature wasn’t value-adding?

Page 32: Effective Teams

There is nothing so useless

as doing efficiently that

which should not be done at all

Peter Drucker

Page 33: Effective Teams

Product management is our job too

Page 34: Effective Teams

The client isn’t always right

Page 35: Effective Teams

More than a half the features in large software

products go unused

Source: Victor R. Basili, Barry Boehm, COTS-Based Systems Top 10 List

Page 36: Effective Teams

Efficient doesn’t mean

effective

Page 37: Effective Teams

Processing the waste

more effectively is

cheaper, neater, faster waste

Stephen Parry

Page 38: Effective Teams

Teamwork

Page 39: Effective Teams

What makes one a great candidate?

Page 40: Effective Teams

Technical skills?

Page 41: Effective Teams

Craftsmanship?

Page 42: Effective Teams

Communication skills?

Page 43: Effective Teams

Learning?

Page 44: Effective Teams

Something else?

Page 45: Effective Teams

Superhero

Page 46: Effective Teams

in·tel·li·gence noun \in-ˈte-lə-jən(t)s\

(1) : the ability to learn or understand or to deal with new or trying situations : reason; also : the skilled use of reason (2) : the ability to apply knowledge to manipulate one's environment or to think abstractly as measured by objective criteria (as tests)

Souce: http://www.merriam-webster.com/dictionary/intelligence

Page 47: Effective Teams

Intelligence is fragile

Page 48: Effective Teams

Intelligence versus

Collective Intelligence

Page 49: Effective Teams

How are individual and

collective intellingece correlated?

Page 50: Effective Teams

There’s no connection between individual intelligence and collective intelligence

Source: Anita Woolley: Collective Intelligence in Human Groups

Page 51: Effective Teams

Collective intelligence trumps individual intelligence

Page 52: Effective Teams

Collective intelligence was

much more predictive in terms of

succeeding in complex tasks than average

individual intelligence or maximal

individual intelligence

Anita Woolley

Page 53: Effective Teams

Indicators of collective intelligence

Source: Anita Woolley: Collective Intelligence in Human Groups

Page 54: Effective Teams

Indicators of collective intelligence

Social perceptiveness

Source: Anita Woolley: Collective Intelligence in Human Groups

Page 55: Effective Teams

Indicators of collective intelligence

Social perceptiveness Communication quality

Source: Anita Woolley: Collective Intelligence in Human Groups

Page 56: Effective Teams

Indicators of collective intelligence

Social perceptiveness Communication quality

Moderate cognitive style diversity

Source: Anita Woolley: Collective Intelligence in Human Groups

Page 57: Effective Teams

Cognitive styles

Object viualizers (visual arts) Spatial visualizers (engineering)

Verbalizers (humanities)

Source: O. Blazhenkova, M. Kozhevnikov: The New Object-Spatial-Verbal Cognitive Style Model

Page 58: Effective Teams

How would you feel about

working with women in your

team?

Page 59: Effective Teams

The more women the better collective intelligence*

Source: Anita Woolley: Collective Intelligence in Human Groups

Page 60: Effective Teams

Indicators of collective intelligence

Social perceptiveness Communication quality

Moderate cognitive style diversity

Source: Anita Woolley: Collective Intelligence in Human Groups

Page 61: Effective Teams

It’s not just diversity; it’s gender

Page 62: Effective Teams

What team size makes it most

effective?

Page 63: Effective Teams

Bigger teams have better collective intelligence*

Source: Anita Woolley: Collective Intelligence in Human Groups

Page 64: Effective Teams

There’s no difference in productivity or quality between teams of 5-9 and 10-12 people

Source: Larry Maccherone: Quantifying the impact of Lean, Kanban, and Agile practices

Page 65: Effective Teams

What is knowledge work?

Page 66: Effective Teams

Sofware development is a team sport

Page 67: Effective Teams

Takeaways

Page 68: Effective Teams

Effective work often means doing stuff that we wouldn’t normally do

Page 69: Effective Teams

Visualization helps to

understand work and spot problems

Page 70: Effective Teams

WIP limits help to improve short term and long term

Page 71: Effective Teams

2O

Page 72: Effective Teams

Collective intelligence trumps individual intelligence

Page 73: Effective Teams

Social perceptiveness

Evenness of communication

Moderate diversity of cognitive styles

Page 74: Effective Teams
Page 75: Effective Teams

Thank you I wish you more women (in teams)

and less work (in progress)

Pawel Brodzinski brodzinski.com

lunarlogic.io

@pawelbrodzinski