So you want to go Git, but other stakeholders in your organization aren't quite convinced it's worth the effort? This talk will explain why migrating to Git is a win for the whole business – not just developers. We'll give you the ammunition you need to convince your team that the switch to Git is a no-brainer.

1. #atlassian

2. The business case for
The business case for Git
It’s not (just) about developer happiness
Tim Pettersen • Developer Provocateur • Atlassian • @kannonboy

4. for business Photo: Hpeterswald

5. Marcus Bertrand
Don’t fear the branch
!
!
!
Stefan Saasen
Scaling git
!
!
!
Sarah Goff-Dupont
Super-powered git+CI
!
!
!
More ?
Nicola Paolucci
Becoming a git master
!
!
!

6. The business case for
SHIPPING IT
CODE QUALITY
DEVELOPER PRODUCTIVITY
KILLER COLLABORATION
BUSINESS RISK

7. Wranglin’ Release
Photo: Colin Gray

8. Linear workflow
JIRA-123
JIRA-456

9. Branching workflow
master
feature/JIRA-123

10. Branching workflow
master
feature/JIRA-123

11. Branching workflow
feature/JIRA-123
isolated feature work
master

12. Branching workflow
feature/JIRA-123
stable master branch
isolated feature work
master

13. git vs centralized

14. 40
30
20
10
git centralized
Daily Weekly Monthly Quarterly Yearly
Source: Atlassian Git Survey 2013
git vs centralized

15. Photo: Daniel Ramirez
Shipping
releases

16. The
Business
Case
• Git makes releasing easier and more regular
• Regular releases are good for everybody

17. Code Quality

18. Quality

19. Quality
n. koâla tēa

20. Quality
n. koâla tēa

21. Photo: Yogi (Flickr)
RCeovdieew

22. Reviews and releases
40
30
20
10
Code Review No Code Review
Daily Weekly Monthly Quarterly Yearly
Source: Atlassian Git Survey 2013

24. Better
Code

25. Better
Code
Shared
Knowledge

26. Better
Code
Shared
Knowledge
Team
Ownership

27. Developer guilt
G =
1
R+1

28. Team
Ownership

29. Team
Ownership

30. Team
Ownership

31. </rant>

32. Code review

33. Pull requests

34. Pull requests

35. Pull requests
review before merging

36. We Don’t Need Code Review…
We Have Continuous Integration!
WELL INTENTIONED (BUT INCORRECT) DEVELOPER
”
“

37. Pull requests

38. Pull requests

39. Pull requests

40. Pull requests
technical debt

41. Pull requests
O(n!) algorithm
technical debt

42. Pull requests
bad API decision
O(n!) algorithm
technical debt

43. Pull requests
bad API decision
“what-evs”
O(n!) algorithm
technical debt

44. Pull requests
human judgement needed
bad API decision
?
“what-evs”
O(n!) algorithm
technical debt

45. Pull request enforcement

46. Pull request enforcement

47. Pull request enforcement

48. The
Business
Case
• Code review shortens time to release
• Code review reduces business risk
• Code review and CI complement each other

49. Unblock
developers
Photo: Dwight Sipler

53. Branch name
pre-populated

54. Is the branch green?
Branch name
pre-populated

55. Confounding build breakages
master

56. Confounding build breakages
master

57. Confounding build breakages
master

58. Confounding build breakages
master

59. Confounding build breakages
master

60. Confounding build breakages
bugfix/JRA-1
master

61. Confounding build breakages
bugfix/JRA-1
master

62. Confounding build breakages
bugfix/JRA-1
master

63. Confounding build breakages
bugfix/JRA-1
master

64. Confounding build breakages
bugfix/JRA-1
master

65. Is the branch green?

66. Comic: Randall Munroe http://xkcd.com/303/

67. Comic: Randall Munroe http://xkcd.com/303/
“I’m running the tests”

68. Building branches
always build master
master

69. automatically triggered
Building branches
always build master
master

70. The
Business
Case
• Server-side branching is crazy… like a fox
• Git makes developers more productive
• Running CI on branches saves a lot of time

71. Photo: Photographer's Mate 3rd Class Eric S. Garst
Collaborate
better

72. Circle of
Trust
Photo: Aljaz Zajc

73. Core dev
team
Circle of
Trust

74. Interns
Other
product
teams
Core dev Support
team
Circle of
Trust

75. Contractors
Interns
Strangers on the
internet
Other
product
teams
Core dev Support
team
Circle of
Trust

76. Collaborating with SVN
Core dev
team

77. Collaborating with SVN
Core dev
team
Everyone
else

78. Collaborating with SVN
Core dev
team
emailing patches
repository tarballs
hell-ish conflicts
Everyone
else

79. Collaborating with forks
Core dev
team
Everyone
else

80. Collaborating with forks
Core dev
team
Everyone
else

81. Collaborating with forks
Core dev
team Changes
Everyone
else
automatically
synchronize
downstream

82. Collaborating with forks
Core dev
team Changes
Everyone
else
automatically
synchronize
downstream
.. but must
be reviewed
before moving
upstream

83. Mentoring with branches
Senior
developers
Junior
developers
master

84. Mentoring with branches
feature/*
Senior
developers
Junior
developers
master

85. Mentoring with branches
feature/*
Senior
developers
Junior
developers
master

86. Mentoring with branches
feature/*
Senior
developers
Junior
developers
master

87. Contractors
Interns
Strangers on the
internet
Other
product
teams
Core dev Support
team

88. Contractors
Interns
Strangers on the
internet
Other
product
teams
Core dev Support
team

89. Contractors
Interns
Strangers on the
internet
Other
product
teams
Core dev Support
team

90. Contractors
Interns
Strangers on the
internet
Other
product
teams
Core dev Support
team

91. The
Business
Case
• Collaboration used to be hard
• Forks make external collaboration easy
• Branch permissions are great for mentoring

92. Business
Risk Photo:Remi Maupetit

93. Don’t lose your
investment

94. Don’t lose your
investment

95. Don’t lose your
investment

96. Don’t lose your
investment

97. Centralized SVN Centralized DVCS

98. Centralized SVN Centralized DVCS
?
?
? ?
?
?

99. Centralized SVN Centralized DVCS
?
?
? ?
?
?

100. Decaying branches

101. Decaying branches
failed experiments?

102. Implementing git
is a business risk

103. Implementing git
NOT
is a business risk

104. VCS marketshare 2014
9% 48% 37%
Source: Black Duck https://www.openhub.net/repositories/compare

105. VCS marketshare 2014
9% 48% 37% 2%
Source: Black Duck https://www.openhub.net/repositories/compare

106. All sorts of teams are on
&

109. The
Business
Case
• Git helps you track R&D more easily
• Git is widely used in the industry
• Switching to Git will help your hiring effort

110. Thank you!
Tim Pettersen • Developer Provocateur • Atlassian • @kannonboy