The document discusses recommendations for effective code review practices in 2018. It begins by noting declining satisfaction with code quality and timely releases. It then discusses 1) conducting daily code reviews using tools like Collaborator, 2) thinking of code reviews as time-savers, and 3) setting clear expectations for code and document reviews. The document also recommends tracking review metrics and fostering a collaborative culture.

1. The Keys to Code Review in 2018

2. Patrick Londa
MarketingManager,Collaborator
SmartBearSoftware
Jonathan Fortunati
SalesEngineer,Collaborator
SmartBearSoftware

3. The Leader In Software
Quality Tools For Teams
Our unique approach infuses quality and speed into your entire
software development lifecycle, so teams can work together to
create the best software on the planet, faster than ever.
• AccelerateDev/Test/OpsWorkflows
• ImproveQualityatEveryStage
• ReduceComplexity
• GainEnd-to-EndVisibility
• ImproveReleaseConfidence
• ReduceCosts

4. Integrations …100 +
Perform Code
and Doc Review
Collaborator
Design, Develop, and
Document APIs
SwaggerHub
UI
API
DEV TEST OPS
Code Script
Run Tests On Real Devices
in the Cloud
CrossBrowserTesting
Create Web Load Tests
LoadComplete
Spec
Create Automated API Functional Tests
(REST, SOAP, and more)
SoapUI Pro Script
Virtualize API and
Database Services
ServiceV Pro
Create API Load Tests
LoadUI Pro
Monitor Web and API Performance,
Availability, and Functional Correctness
AlertSite
Manage Manual and
Automated Tests
QAComplete
Collaborate on an Idea using BDD, Test
Continuously, and Generate Living Docs
HipTest
TestComplete
Create Automated UI
Functional Tests
(Web, Desktop, Mobile)
Create Automated UI
Tests in IDE Using BDD
TestLeft

5. Agenda
• The Code Review Process and Perceptions
• The DevelopmentStack in 2018
• TeamFirmographics and Beliefs
• Recommendationsfor Your Team
• Peer Review in Collaborator

6. The Code Review
Process & Perceptions

7. Satisfaction with code quality and timely releases are on the decline.
The 2018 State of Code Review

8. The 2018 State of Code Review

9. The 2018 State of Code Review

10. The 2018 State of Code Review

11. The 2018 State of Code Review

12. The 2018 State of Code Review

13. The 2018 State of Code Review

14. The 2018 State of Code Review

15. The 2018 State of Code Review

16. The 2018 State of Code Review

17. The 2018 State of Code Review

18. The Development
Stack in 2018

19. The 2018 State of Code Review

20. The 2018 State of Code Review

21. The 2018 State of Code Review

22. The 2018 State of Code Review

23. The 2018 State of Code Review

24. Team Firmographics
and Beliefs

25. The 2018 State of Code Review

26. The 2018 State of Code Review

27. The 2018 State of Code Review

28. The 2018 State of Code Review

29. The Keys

30. The 2018 State of Code Review
1. Don’t worry about what repository
management tool your team is using.

31. The 2018 State of Code Review

32. The 2018 State of Code Review
1. Don’t worry about what repository
management tool your team is using.
2. Conduct code reviews on a daily basis.

33. The 2018 State of Code Review

34. The 2018 State of Code Review
1. Don’t worry about what repository
management tool your team is using.
2. Conduct code reviews on a daily basis.
3. Think of code reviews as a time saver.

35. The 2018 State of Code Review

36. The 2018 State of Code Review
1. Don’t worry about what repository
management tool your team is using.
2. Conduct code reviews on a daily basis.
3. Think of code reviews as a time saver.
4. Conduct tool-based reviews.

37. The 2018 State of Code Review

38. The 2018 State of Code Review
1. Don’t worry about what repository
management tool your team is using.
2. Conduct code reviews on a daily basis.
3. Think of code reviews as a time saver.
4. Conduct tool-based reviews.
5. Set clear expectations for both code and
document reviews.

39. The 2018 State of Code Review

40. The 2018 State of Code Review
1. Don’t worry about what repository
management tool your team is using.
2. Conduct code reviews on a daily basis.
3. Think of code reviews as a time saver.
4. Conduct tool-based reviews.
5. Set clear expectations for both code and
document reviews.
6. Use tool-based reviews in conjunction
with meeting-based reviews.

41. The 2018 State of Code Review
1. Don’t worry about what repository
management tool your team is using.
2. Conduct code reviews on a daily basis.
3. Think of code reviews as a time saver.
4. Conduct tool-based reviews.
5. Set clear expectations for both code and
document reviews.
6. Use tool-based reviews in conjunction
with meeting-based reviews.
7. Choose review metrics to track and make
reporting part of your process.

42. The 2018 State of Code Review

43. The 2018 State of Code Review
1. Don’t worry about what repository
management tool your team is using.
2. Conduct code reviews on a daily basis.
3. Think of code reviews as a time saver.
4. Conduct tool-based reviews.
5. Set clear expectations for both code and
document reviews.
6. Use tool-based reviews in conjunction
with meeting-based reviews.
7. Choose review metrics to track and make
reporting part of your process.
8. Foster a collaborative culture.

44. Collaborator
The peer review platform for
quality-first teams

45. Collaborator is the only enterprise-grade peer code and document review tool, built
to:
• Standardize thepeer review workflows that work best for you
• Reducesoftware defects early and often
• Ease compliance burdens & improve traceability
• Shorten development time to market
The Peer Review Solution for Quality Critical Teams

46. Question & Answer Time
Type any questions you haveinto the Zoom
Q&A box.

47. Thank you for joining!
You canstart a freetrialof Collaboratortoday at SmartBear.com.