The document outlines a talk by Sven Peters on effective software development practices, emphasizing the importance of Agile methodologies and collaboration among team members. It advocates for continuous improvement, quality responsibility shared across all roles, and the integration of feedback loops to enhance development efficiency. The text also humorously addresses misconceptions in software development and encourages a culture of openness and innovation within teams.

1. How to do
Kick-Ass
Software Development
@svenpet

2. Who expects to see some code?

3. System.out.println
("Sorry, you may leave now");

4. Who expects to learn a new
methodology?

5. There is no Kick-Ass manifesto!
...and no certification

6. Who just wants to kick ass?

7. Yes, that's me ;)
THIS IS YOUR TALK

8. How to do kick ass development?

9. Use Java

10. Use Java
...is not so important

11. Sven Peters
Atlassian Ambassador
svenpet.com
@svenpet

12. better software
less overhead
faster development
happy customer
happy developers
Agile

13. What's the state of
Agile
2013 ?

15. The Dark Manifesto of Agile Software
Development
We are uncovering better the only ways of developing
software by doing it and helping teaching others do it.
Through this work we have come to value:
Individuals and interactions over and not processes and tools
Working software over and not comprehensive documentation
Customer collaboration over and not contract negotiation
Responding to change over and not following a plan
That is, while since there is no value in the items
on the right, we value only the items on the left more.

16. Programming, Motherfucker
Do you speak it?

17. Is
Agile
dead?

18. The Gartner Hype Curve
Agile?

19. We need
some smart people!
Guru

20. Stop following the next guru
and kick-ass again

21. legacy teams think...
adding processes helps
changing stuff is too complicated
old decisions still apply
ONE WAY

22. Let's improve!
and kick-ass again

23. legacy teams think...
I don't give a #@!%
NO WAY

24. Ass
Deliver Kick-Ass Software
One Kick-Ass Team
Kick-Ass Collaboration
Kick-Ass Automation
Kick
ing
Topi
cs

25. Deliver
Kick-Ass Software

26. Building the right thing
before
How do we know?
Microsoft Kin

27. Fake it
til you
Make it

28. Speech-to-Text Experiment

29. even one step before that....
Paper
Prototypes

31. Software
ea Ar
n
Con
ctio
tru
s
ovin
pr
Im
are
oftw
gS

32. Generate a kick-ass
Feedback
Experience

33. Easy to find
Make it simple
Fast to submit

34. GOT FEEDBACK?

35. GOT FEEDBACK?

36. GOT FEEDBACK?
Got Feedback?
Rate the page *
What do you like? *
What needs to be
improved?*
Awesome
Good
Good tools, but this talk doesn't kick ass at all!
Add more jokes!
Browse
Upload a screenshot
Name
Freddy Eedback
Email
f.eedback@complain.com
Submit
Meh!
Cancel
Bad
Horrible

37. GOT FEEDBACK?
Easy to find
Got Feedback?
Rate the page *
What do you like? *
What needs to be
improved?*
Awesome
Good
Good tools, but this talk doesn't kick ass at all!
Browse
Name
Freddy Eedback
Email
f.eedback@complain.com
Cancel
Bad
Horrible
Make it simple
Fast to submit
Add more jokes!
Upload a screenshot
Submit
Meh!

38. Protect
your Developers

39. The Sh*t umbrella
425 million user
100 developer

40. We're not doing

41. Everyone
On The
Front Line

42. Feedback
Close the Loop
and get pers nal

43. Developers
on
Support

44. Care about your customers!
Have an effective feedback loop
Keep improving!

45. One
Kick-Ass Team

46. Different
Developer
Roles
Responsibilities
Tester

47. The P
roble
Bottlenecks : Accountability : Scalability
Developer
Tester
ms

48. Developer
on
DoT
Test

49. So the developers are
doing all the work?

50. QA
Qual·i·ty As·sis·tance [kwol-i-tee] [uh-sis-tuh ns]
Quality is everybody's responsibility. QA employees help and train
developers to become better tester, testing the more complicated stuff,
creating test data, investigating in new test tools and working on test
strategies.

51. 6 Tips
for kick-ass DoTing

52. 1. Training

53. 2. Pairing

54. 3. Blitz Test

55. 4. Test Recipe*
* advanced doting

56. 5. Split Sessions*
* advanced doting

57. 6. Bug Hunter*
* advanced doting

58. Quality is everybody's responsibility

59. Developers
are doing
Design

60. Developers
are doing
Design

61. Whyshould we have designers?
Because we suck!

62. Scaling Designers?
Designer
Designer
?
?

63. Scaling Designers?
Use Developers FTW!
Designer
Designer
Developer
Developer

64. Our developers need some
Design guidance!

65. Design Guidelines
Just a few controls
Simple rules
Tools to test design
Dev Speed
Kick-Ass
https://developer.atlassian.com/design/

66. Design Workshop
for Developers

67. Developers
are
Designers

68. Designers
Developers
removing friction

69. Developers
are
Desig
ner in
are
Designers
code

70. Department barriers slows you down!
Work together as one team!
Keep improving!

71. Kick-Ass
Collaboration

72. Lonesome Cowboy Coder

73. The trouble starts
with the team

76. Traffic Rules
are protecting us from accidents

77. Development Rules
are protecting us from making mistakes

79. BRANCH
PULL
MERGE

80. A branch
for every task

81. Branches
have short lives
average 2 days

82. we use
Pull Requests
what do you
think?

83. feel better
learn
better quality
blame
Why do you want to discuss
your code changes?

84. fast approvals
2+
moving fast

85. we prefer
Collocated
Teams

86. the truth is
It's not always
possible

87. Where
do you work best?
...in the office?
...in the coffee bar next door?
...on your couch at home?
it dep
ends

88. How
do you communicate
effectively?

89. offline
Emails
one to many
asynchronous
add people

90. Are you
crazy
?

91. too

92. Prob
are bad for conversations
lots of spam
lems
Emails
often too long
needs an action

93. Prob
are bad for conversations
lots of spam
lems
Emails
often too long
needs an action

94. Who uses
Chat
?

95. Confluence
Developer
Design Team
Enterprise
Discussions
Beer Drinkers
Just the conversations you need to kick ass
Chat Rooms

96. Chat
is great for remote conversations
...and local!
People can stay in the zone

97. Chat
is great for different timezones
The chat records all conversations that happened during the night

98. Chat
can pull people into the conversation
with ease
Just @mention someone

99. Choose your tools wisely

102. Camera
We built portals!
TV
Mac mini

103. Remove collaboration friction.
Easy workflows -> fast development
Keep improving!

104. Kick-Ass
Automation

105. We're helping people
to be faster
by automating their work

106. How much time do you spend a week
to automate your software development?

107. Who is doing continuous integration?

108. Who kick-ass continuous integration?
is doing

109. Our builds
sucked
took to long
were too complicated
were unstable
missed a concept

110. Fail Fast

111. 4 things how to tame monster builds
and kick-ass again

112. 1. Pass the artifact

113. 2. Parallelize Tests

114. 3. Have a build strategy
performance tests
platform tests
nightly builds
less frequent (every hour)
building + unit & UI tests
every check in

115. Data Porn
4. Look at your stats!

116. Care a
bout a
u
tomati
on
Faster builds >>
less task switching

117. More automation
awesomeness!

118. Flakey Test Detector
de up
his si
T
st
Te
ey
lak
F
re
with
andle
H
ca

119. Wallboards

120. Freud Bot

121. Use your skills to automate things!
Keep improving!

122. Release Button
single push deployment

123. Deliver Kick-Ass Software
One Kick-Ass Team
Kick-Ass Collaboration
Kick-Ass Automation

124. Kick-Ass Software Development

125. Kick-Ass Software Development
Kick-Ass customers
Kick-Ass team
Kick-Ass dev speed
Kick-Ass quality
Kick-Ass scale

126. Kick-Ass Software Development
Kick-Ass customers
Kick-Ass team
Kick-Ass quality
Kick-Ass dev speed
Kick-Ass scale

127. Is
Agile
dead?

128. Be excellent
in everything you do

129. Managers
are humans, too!
harder
easier

130. Share & failures
success

131. Build a kick-ass culture

132. Step out of your comfort zone
and be more awesome

133. Did you
kick ass
today?

134. Thanks!
svenpet.com/talks
@svenpet