The document discusses how to do kick-ass software development through agile practices like using Java, improving as a team, collaborating well, automating tasks, and building a kick-ass culture. It emphasizes delivering high quality software quickly through a co-located team with simple workflows, chat for communication, continuous integration, handling flaky tests, and deploying with a single button press. The overall message is that focusing on developer happiness, customer satisfaction, and continual improvement will result in kick-ass software development.

1. How to do
Kick-Ass
Software Development

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. THIS IS YOUR TALK
Yes, that's me ;)

8. How to do kick ass development?

9. Use Java

10. Use Java
...is not so important

11. Sven Peters
Atlassian Ambassador
@svenpet
svenpet.com

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

13. Agile2013 ?
What's the state of

15. 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.
The Dark Manifesto of Agile Software
Development

16. Programming, Motherfucker
Do you speak it?

17. Agile
Is
dead?

18. The Gartner Hype Curve
Agile?

19. some smart people! Guru
We need

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

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

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

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

24. Deliver Kick-Ass Software
Kick-Ass Automation
One Kick-Ass Team
Kick-Ass Collaboration
Ass Kicking Topics

25. Deliver
Kick-Ass Software

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

27. Fake it
til you
Make it

28. Speech-to-Text Experiment

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

31. SoftwareConstruction Area - Improving Software

32. Feedback
Generate a kick-ass
Experience

33. Make it simple
Easy to find
Fast to submit

34. GOT FEEDBACK?

35. GOT FEEDBACK?

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

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

38. Protect
your Developers

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

40. We're not doing

41. Everyone
On The
Front Line

42. Close the Loop
Feedback
and get pers nal

43. Developers
on
Support

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

45. Kick-Ass Team
One

46. Developer
DifferentRoles
Responsibilities
Tester

47. Developer Tester
The Problems
Bottlenecks : Accountability : Scalability

48. DoT
Developer
on
Test

49. So the developers are
doing all the work?

50. 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.
QA

51. 6 Tipsfor 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. Qualityis everybody's responsibility

59. Design
Developers
are doing

60. Design
Developers
are doing

61. should we have designers?
Why

62. Designers?Scaling
Designer Designer ? ?

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

64. Our developers need some
Design guidance!

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

66. DesignWorkshopfor Developers

67. Designers
Developers
are

68. DevelopersDesigners
removing friction

69. Designers
Developers
areare
Designer in code

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

71. Collaboration
Kick-Ass

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

78. Process Process Process Process Process Process Process Process Proc
Process Process Process Process Process Process Process Process
rocess Process Process Process Process Process Process Process Proces
Process Process Process Process Process Process Process Process Proc
rocess Process Process Process Process Process Process Process Proces
cess Process Process Process Process Process Process Process Process
cess Process Process Process Process Process Process Process Process
Process Process Process Process Process Process Process Process Proce
Process Process Process Process Process Process Process Process Proc
ocess Process Process Process Process Process Process Process Process
rocess Process Process Process Process Process Process Process Proces

79. Fast + Simple
Workflow
For Parallel Coding
Coding

80. A branch
for every task

81. Branches
have short lives
average 2 days

82. we use
Pull Requests
what do you
think?

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

84. fast approvals
moving fast
2

85. Collocated
Teams
we prefer

86. It's not always
possible
the truth is

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

88. do you communicate
How
effectively?

89. Emails
asynchronous
offline
one to many
add people

90. Are you
crazy?

91. too much

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

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

94. ChatWho uses ?

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

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
Just @mention someone
with ease

99. Choose your tools wisely

102. We built portals!
Mac mini
TV
Camera

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

104. Automation
Kick-Ass

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. Whois doing continuous integration?

108. Whois doing kick-ass continuous integration?

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

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
building + unit & UI tests every check in
platform tests less frequent (every hour)
performance tests nightly builds

115. 4. Look at your stats!Data Porn

116. Faster builds >>
less task switching
Care about automation

117. More automation
awesomeness!

118. Flakey Test
Handle with care
This side up
Flakey Test Detector

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
Kick-Ass Automation
One Kick-Ass Team
Kick-Ass Collaboration

124. Kick-Ass Software Development

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

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

127. Agile
Is
dead?

128. Be excellent
in everything you do

129. Managers are humans, too!
easier
harder

130. Sharesuccess & failures

131. Builda kick-ass culture

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

133. Did you
kick ass
today?

134. Thanks!
@svenpet
svenpet.com/slides