Download as PDF, PPTX
Uploaded bySven Peters
Kick-@$$ Sofware Development
The document discusses the importance of effective collaboration in software development, emphasizing the need for teams to communicate and work together efficiently. It highlights the role of code reviews and feedback loops in improving the software development process and ensuring high-quality outcomes. The presentation encourages teams to adopt tools and practices that foster teamwork and transparency for successful project execution.
More Related Content
Similar to Kick-@$$ Sofware Development
Kick-@$$ Sofware Development
- 1. Kick-@$$ Software Development SVEN PETERS • LEAD EVANGELIST • ATLASSIAN • @SVENPET
- 2. Sven Peters LeadEvangelist @svenpet
- 4.
- 5.
- 6. 1,000 Atlassian’s helping 40,000 Companies
- 7. Development Teams Plan Collaborate Code Release
- 8. Development Teams Support Teams HR, Finance & Legal Teams
- 9.
- 10. Every Team should Kick-@$$
- 11.
- 12. Our customers Emma William
- 13. Our customers Emma William FAKE
- 14.
- 16. We stick thoseon walls
- 17. Reminds us whowe built the software for
- 18.
- 19. Fake it tilyou Make it
- 20. before we builtthings… Paper Prototypes
- 22. Software Software Improving- Construction Area
- 23. Generate a Kick-@$$ Feedback Experience
- 24.
- 25.
- 26. GOT FEEDBACK? GotFeedback? Rate the page * Awesome Good Meh! Bad Horrible What do you like? * Good tools, but this talk doesn't kick @$$ at all! What needs to be improved?* Add more jokes! Upload a screenshot Browse Name Email Freddy Eedback f.eedback@complain.com Submit Cancel
- 27. GOT FEEDBACK? GotFeedback? Rate the page * Awesome Good Meh! Bad Horrible Make it simple What do you like? * Good tools, but this talk doesn't kick @$$ at all! What needs to be improved?* Add more jokes! Upload a screenshot Browse Name Email Freddy Eedback f.eedback@complain.com Submit Cancel Easy to find Fast to submit
- 28.
- 29. 15 years ago Software Development spec code build
- 30.
- 31.
- 32.
- 33. code code track code design operate
- 34. it’s not thateasy… JUST LET ME CODE!
- 35. Software is complexnowadays
- 36. Each developer hasa copy
- 37. A branch forevery task
- 38. Get Coding! Story assigned
- 39. Branches have shortlives average 2 days
- 40. Merging changes together small changes &
- 41.
- 42. branch code merge repeat
- 43.
- 44. branch code merge start progress done
- 45. JUST LET MECODE!
- 46. branch code merge start progress done
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56. we can’t kick-@$$on our own The Kick-@$$ Team
- 58. Who has seenthe Gorilla? Who has seen the curtain changed color? Who has seen a black shirt player leaving?
- 60. We just seethings we expect!
- 61.
- 62. boring Code ReviewSessions
- 63.
- 64. Code Reviews theright way
- 65. 1 Auto qualitycheck please review my code some obvious problems Code Reviews
- 66. 1 Auto qualitycheck check in code please review automatic check Code Reviews
- 67. Code Reviews toolate 2 At the right time branch code merge
- 68. 2 At theright time Code Reviews branch code review merge
- 69. At the righttime a view into the future 3 Code Reviews
- 70. Asynchronously Reviewer 1Reviewer 2 Reviewer 3 3 Code Reviews
- 71. 3 Asynchronously CodeReviews
- 72. Keep the flow 4 0 4 Code Reviews
- 73. Keep the flow 4 12 0 4 Code Reviews
- 74. 42 Keep theflow merge when min. approvals 4 Code Reviews
- 75. Software development isa team effort
- 76. me team Youneed both to kick-@$$
- 77.
- 78. Best way tocollaborate?
- 79. Everyone in oneroom!
- 80. Don’t forget todocument
- 81. Not important foreveryone
- 82.
- 83. More important thingsto do?
- 84.
- 85.
- 86. Connect with theteam Chat team chat rooms
- 87. Re Connect zz z Chat chat room history
- 88. Connect with othersChat @mention people
- 89. Connect your systemsChat integration & bots
- 91. Connect the wholeChat organization more transparency
- 92.
- 93. Are you readyto Kick-@$$ ?
- 94. This Way ThisWay This Way Maybe there are better ways
- 95. Be excellent ineverything you do
- 96. Be the change you seek
- 97.
- 98.