2. 7 Ways To Make Good Teams Great
TEAM MOTIVATION AND COLLABORATION
SVEN PETERS
•
AMBASSADOR
•
ATLASSIAN
•
@SVENPET

3. That‘s
me
Sven Peters
Atlassian Ambassador
speters@atlassian.com
@svenpet
svenpet.com

4. How To Make
Software Teams Great?

5. How To Make
Agile Teams Great?

6. How To Make
Good Teams Great?

7. Programmers Heaven
We kick ass
Kick Ass Team
Kick Ass Product

8. s
ie
n
t
a
a
h
p
W
m
o
C
o
d

9. s
ie
n
t
a
a
h
p
W
m
o
C
o
d

10. s
ie
n
t
a
a
h
p
W
m
o
C
o
d
motivation to become great?

11. s
ie
n
t
a
a
h
p
W
m
o
C
o
d
great talents but limited

12. at
h
W
e
w
n
a
c
o
d

13. at
h
W
e
w
n
a
c
o
d

14. at
h
W
e
w
n
a
c
o
d

15. e
g
n
a
h ek
e
c
B
e se
h u
t
o
y

16. 7
Ways
To Make
Good Teams

17. 1
F
‘s
It
e
im
t
w
lo

18. Produc tivity

19. Produc
tivity

20. NUMBERS
2 80
hours/day
recovering from distractions
%
of interruptions are
considered trivial
Source: atlss.in/TimeWaster

21. vs.

22. disturb
Time
Do not

23. Sit down, we
need to talk

24. disturb
the rest
Do not
Chat

25. Chat
is great for silent conversations
People can stay in the zone

26. Confluence
Developer
Design
Team
Chat
Rooms
connect teams silently
Enterprise
Beer

27. Chat
can pull people into the conversation
Just @mention someone

28. disturb
the rest
Do not
Chat
turn it off and read it later!

29. 10:00am:
Work in Pajamas: Winning at Remote Distributed Teams
Chat
Patti Chan
Intridea

30. Reality Check:
How easy is it to implement in a corporate
environment?
Feasibility Points:
Awesomeness Points:
How great will your team be?

31. d
you
r
Brai
n
Fee
2

32. o
ze
ni
a
rg
Coding Sessions

33. o
ze
ni
ga
r
Brown Bags

34. Reality Check:
Feasibility Points:
Awesomeness Points:

35. 3
Say:
Well

36. Appreciation
also of
small things

37. Appreciation
is important for
happiness

38. Appreciation
made
public

39. Appreciation
for
everybody

40. Appreciation
without
approval

41. „
Feel free to recognize someone for
something awesome they've done (no
approval required!) To recognize a
colleague, please click here.
Atlassian Extranet

43. Reality Check:
Feasibility Points:
Awesomeness Points:

44. 4
R
eport
obot

45. d
l
i
w
ec
ll
ng
ti
d
ta
a
e
r
‘E
eSuva stosmere e
PhTestserver m
Cuu
ppAa
oFadIletsaffics
ll d
W LA eaonr im i
VBptTc T
neorTT w
e eueutaae
i scinvs
ivsese
o
reissi
icdter tnew
l
blfn cm s
SCtpsa a i tyo
a ec Re
i
ySo
e
W
s
Performance s
ooTime
edmple
Cc
R
ted
ab
co
t
ou

46. W
e
e
r
‘
ab
t
ou
d
l
i
w
t
au
a
om
ed
t
re
o
p
ts
r

47. W
e
e
r
‘
ab
d
l
i
w
a
sh
ut
o
g
r in
d
ta
a
Is it hot in here, or is it my
Information
Radiator
?
Alistair Cockburn

48. Reality Check:
Feasibility Points:
Awesomeness Points:

49. 5
Eat
your own
Dog Food

50. T
g
n
i
t
s
e

51. e
B
t
t
r
e

52. R
t
l
u
s
e

53. Eating
your own
Dog Food
is alpha testing

54. Eating
your own
Dog Food
is understanding

55. Eating
your own
Dog Food
is painful

56. Eating
your own
Dog Food
is fast feedback

57. d
o
g
n
i
D
o @ Atlassian
f
g
o

58. Reality Check:
Feasibility Points:
Awesomeness Points:

59. 6
Do a
special
day

60. Unpleasant
Things

61. Forget
about the
current
Sprint
for a day

62. technical writer
technical writer
Doc Sprint

63. Blitz Test
fearless tester

64. Clean Up Day

65. Get stuff
out of
the door

66. Reality Check:
Feasibility Points:
Awesomeness Points:

67. 7
Experimentation
Time

68. To achieve great things, two
things are needed:
a plan
and not quite enough time.
Leaonard Bernstein

69. Moti vation
Inno
through
vation

70. Idea
Brown Bag

71. Shipment
Order

72. Plan
Sprint Planning

73. coolest
This... is the longest day of my
life

74. Go
Code
:;while [ $? -eq 0 ];do nc -vlp 8080 c'(r=read;e=echo;$r a b c;z=$r;while [ ${#z} -gt
2 ];do $r z;done;f=`$e $b|sed 's/[^az0-9_.-]//
gi'`;h="HTTP/1.0";o="$h 200 OKr
n";c="Content";if [ -z $f ];then($e $o;ls|(while
$r n;do if [ -f "$n" ]; then $e "<a href="/$n
">`ls -gh $n`</a><br>";fi;done););elif [ -f $f
];then $e "$o$c-Type: `file -ib $f`n$c-Length:
`stat -c%s$f`";$e;cat $f;else $e -e "$h 404 Not
Foundnn404n";fi)';done

75. Show
Winner

76. Innovation
Motivation

77. Crappy Code
unstable Feature
Not maintainable
No final Product

78. good Code
It's maintainable
20% time
stable Feature
polished for Product

79. innovation Time
independent Time
own Time

80. JML

81. Conflicts
Dependencies
Workload
Sprint Goals

82. innovation Time
planned Time
team Time
Innovation
Week

83. Reality Check:
Feasibility Points:
Awesomeness Points:

84. 1
It‘s Flowtime
2
Feed your Brain
3
Say: “Well done“
4
Report Robot
5
Eat your own Dogfood
6
Do a Special Day
7
Experimentation Time
7

85. Try
Fail!
but don‘t be
stupid!

86. Measure!

87. Make
it
yours

88. be
Different

89. Thanks!
svenpet.com/talks
@svenpet

90. Rate this Talk
Seven Ways to Make Good Teams Great
Text code below to 22333
or visit http://bit.ly/16JzfzL
MEH = U
NO T BA D = V
P R ET T Y GO O D = W
A WES O ME = X
To join this session, send text 136888 to