When the Atlassian Dev Tools team looked to innovate on continuous integration and delivery, we explored many ways to bring the build and deployment pipeline closer to developers and Bitbucket. This led us to think outside the existing product boundaries of Bamboo and build on top of the Bitbucket Connect platform. James Bryant, a senior designer on the Software Team, will take you through how his team decided to build on top of a platform instead of building out new products. It involves defining a vision, guiding a team with an experience, and testing with customers early and often to build the new Bitbucket Pipelines feature. You’ll come away from this session with a framework for adopting an experience-driven strategy, and tips to help give your agile teams a vision to build on top of a platform. Products covered: Bitbucket, Bamboo

1. JAMES BRYANT • SENIOR DESIGNER • @JAM_SBRYANT
Building on the Shoulders of Giants
the Story of Bitbucket Pipelines

2. Bitbucket Pipelines
NOW AVAILABLE

3. Bitbucket Pipelines

4. NAME • TITLE • COMPANY • @TWITTERHANDLE
Title
Subtitle

5. Automate the process of testing
and deploying software.

6. NAME • TITLE • COMPANY • @TWITTERHANDLE
Title
Subtitle

7. During software development,
developers repeatedly test
functionality and integration
before they package and ship
software. The more often they
test the easier it is to identify

8. test the easier it is to identify
problems, but frequent testing
can slow down development. The
solution is to automate and
parallelize the process of testing
and deploying software in order
to be able to deploy at any time,
fail fast and ship often.

10. There’s got to be a better way…

12. Prototypes are
great at
validating
functionality

13. Prototypes aren’t great
at explaining value

14. Prototypes aren’t great
at explaining value.
Prototypes don’t frame the problem
when they present a solution.

15. Prototypes aren’t great
at explaining value.
Tell a story instead

16. Leo Widrich, Co-founder and COO at Buffer
A story, if broken down into the simplest
form is a connection of cause and effect.
And that is exactly how we think.

17. This is our story

19. DesignerProduct Manager Dev Manager QA Writer
Team lead and developers Team lead and developers

20. DesignerProduct Manager Dev Manager QA Writer
Team lead and developers Team lead and developers

23. Server Cloud

24. Pipelines for CloudServer

25. Server
Pipelines for Cloud
Product

26. Server Pipelines for Cloud
Platform add-onProduct

27. Part 1
The story
Part 2
The platform

28. Part 1
The story
Part 2
The platform

29. Customer research
Market research
Envisioning

30. Customer
research
TIPS

31. Interview chain
Gamified it, talked to one customer
per week. Longest chain of 6 weeks.

32. Non customers
Interview chain
Gamified it, talked to one customer
per week. Longest chain of 6 weeks.
New hires, meet-ups, conferences

33. Team journeys
Non customers
Interview chain
Gamified it, talked to one customer
per week. Longest chain of 6 weeks.
New hires, meet-ups, conferences
Dug into the story of the team.
Identify inflections points
Retrace history

34. Market
research
TIPS

35. Breakfast with the Enemy
Competitive analysis with different
members of the team. Shared and
discussed over breakfast.

36. Breakfast with the Enemy
Competitive analysis with different
members of the team. Shared and
discussed over breakfast.

37. Crunched the numbers
Breakfast with the Enemy
Competitive analysis with different
members of the team. Shared and
discussed over breakfast.
Confirmed a great market
opportunity.
Market
research

38. Envisioning TIPS

39. Envisioning
Regular check-ins
Established a ‘brain trust’ with
leadership to set a regular cadence.

40. Established values
Regular check-ins
Established a ‘brain trust’ with
leadership to set a regular cadence.
Designed mock marketing material
to explain the customer value.

41. Established values
Regular check-ins
Established a ‘brain trust’ with
leadership to set a regular cadence.
Designed mock marketing material
to explain the customer value.

42. Established values
Regular check-ins
Established a ‘brain trust’ with
leadership to set a regular cadence.
Designed mock marketing material
to explain the customer value.

43. Established values
Regular check-ins
Established a ‘brain trust’ with
leadership to set a regular cadence.
Designed mock marketing material
to explain the customer value.

44. Illustration by Abhijeet Wankhade (www.sokratus.in)
Established values
Regular check-ins
Established a ‘brain trust’ with
leadership to set a regular cadence.
Designed mock marketing material
to explain the customer value.

45. Customer research
Market research
Envisioning

46. Customer research Characters
Challenges
Market research Opportunities
Envisioning Solution

47. Prototypes aren’t great
at explaining value.
There was a story to tell

49. Diving into the story
inside the story

54. and back to the first level

55. Characters
Challenges
Opportunities
Solution

56. Making a movie

58. Small team?
Keep it simple.

59. Keynote Powerpoint

60. Keynote Powerpoint
TIPS

61. Keynote PowerpointMagic move
TIPS

62. Keynote PowerpointMagic move Morph
TIPS

63. Keynote PowerpointMagic move Morph
TIPS

64. Keynote PowerpointMagic move Morph
TIPS

65. Small team
Present in person

66. Communicate across company
Automate with a movie

67. For larger ambitions, go bold.

69. Characters

70. Use your personas
for the characters

71. Fears overhead of
maintaining a
complex build and
deployment

72. Harvey in particular has been
championing better CI.

73. Harvey in particular has been
championing better CI.
Where do I start?
What are the three basic things I need to know?
Who can help me?
Are you making it easy for me to take action?
How are my teammates using this?
Are you changing the way I work (without helping me)?
Am I able to predict the outcomes of our work?
Can I see who’s responsible for what?
What are the best practices for doing this?

74. Where do I start?
What are the three basic things I need to know?
Who can help me?
Are you making it easy for me to take action?
How are my teammates using this?
Are you changing the way I work (without helping me)?
Am I able to predict the outcomes of our work?
Can I see who’s responsible for what?
What are the best practices for doing this? Wants a predictable
process for configuring
his builds

75. Team

77. The journey of the team
Grows over time with various
roles and complexity.

79. Who you'll be targeting

80. Who you'll be targeting
Who you'll be opportunistic about

81. Who you'll be targeting
Who you'll be opportunistic about
Who you'll say no to

82. Give it a name.

83. BUILD MY BUCKET

84. BUMBU

85. This story defined our experience.

86. “Experience driven development”

87. Combine people, research
and solution to tell story.

88. Learn more about building product
visions tomorrow:
Painting a Vision for
Your Product
1:50pm Thursday,
Improve & Innovate
Sherif Mansour

89. Combine people, research
and solution to tell story.

90. Part 1
The story
Part 2
The platform

91. Part 1
The story
Part 2
The platform

92. Server Cloud

93. Cloud

95. Number of steps
WAC
6
Atlassian Cloud Setup
17
Configuring
Amazon EC2
40+
First Build
15

96. Number of steps
Bitbucket First Build
5

100. 3 month onboarding roadmap quickly
turned into 6 months6
9

101. 3 month onboarding roadmap quickly
turned into 6 months
6
9
12

102. 3 month onboarding roadmap quickly
turned into 6 months
9
12

103. We spent a lot of time trying to
turn a successful server
application into a cloud service.

104. We spent a lot of time trying to
turn a successful server
application into a cloud service.

105. We weren’t shipping much value
to Bamboo Server customers.

107. Product Product

108. Service Product

109. Service Platform

110. Platform
Add-on
Service

111. Platform
Add-on
Service

112. Platform
Add-on
Service

113. Platform
User management
Design system
Object model
Large user base
Add-on

114. Add-on
Platform
Code storage
History
Branch management
Code editor
Configuration
BONUS

115. These are the giants
we are building on.

116. Agents
Images/containers
Orchestration
Scalability

117. Agents
Images/containers
Orchestration
Scalability

118. Hear more about how we developed
Bitbucket Pipelines tomorrow:
Connect + Docker + AWS
= Bitbucket Pipelines
3pm Thursday,
Platform & APIs Track
Nathan Burrell

119. Add-on
Platform
Move fast.
Focus on our core
experience.

120. Build on your own
Platform
Iterate on internal
feedback faster
Provide a reference
to inspire ecosystem
Prove the value of
your platform
BONUS

121. Server Cloud

122. Server Cloud

123. DesignerPM Dev Manager
Team lead and developers Team lead and developers
DesignerPM Dev Manager

124. Platform enabled us to
focus on delivering the
core value.

125. Part 1
The story
Part 2
The platform

126. The story so far…

128. Takeaways

129. Roadmaps longer than 6 months
can benefit from
Experience Driven Development

130. Considering a rewrite?
Consider building on a platform

131. Building on the shoulders of giants
wasn’t about getting there faster.

132. Focus.

133. Thank you.
JAMES BRYANT • SENIOR DESIGNER • @JAM_SBRYANT