Great products start with great planning. At Atlassian we take a multitude of approaches to plan our feature releases. Learn how you can take some of the practices the Confluence Product Management Team makes use of – such as product requirements, prototypes, customer interviews, and user journeys – to deliver great solutions for your customers.

1. #atlassian

2. SHERIF MANSOUR • PRODUCT GUY • ATLASSIAN • @SHERIFMANSOUR
Do Agile Right
Lessons Learned From an Atlassian Product Manager

3. SHERIF MANSOUR • PRODUCT GUY • ATLASSIAN • @SHERIFMANSOUR
Do Agile Right
Lessons Learned From an Atlassian Product Manager

4. SHERIF MANSOUR • PRODUCT GUY • ATLASSIAN • @SHERIFMANSOUR
Do Agile Right
Lessons Learned From an Atlassian Product Manager
There is no
“right way”

6. Defining the
problem
Building the
solution
Getting
feedback

7. Defining the
problem

10. The Homer

17. 1
Focus roadmap
& development

18. 1
Focus roadmap
& development
2
Create better
experiences

19. 1
Focus roadmap
& development
2
Create better
experiences
3
Improve
marketing

20. 1
Focus roadmap
& development

21. 1
Focus roadmap
& development

22. 2
Create better
experiences

24. 3
Improve
marketing

27. http://bit.ly/ADG-Personas

28. Customer Interviews

29. Building a shared
understanding

32. COMMUNICATE
OBSERVATIONS

33. COMMUNICATE
OBSERVATIONS
INTERPRET
PROBLEMS

34. COMMUNICATE
OBSERVATIONS
INTERPRET
PROBLEMS
CONNECTING
OPPORTUNITIES

35. COMMUNICATE
OBSERVATIONS
INTERPRET
PROBLEMS
CONNECTING
OPPORTUNITIES
V
A
L
U
E

36. COMMUNICATE OBSERVATIONS
CONNECTING OPPORTUNITIES
INTERPRET PROBLEMS

37. COMMUNICATE OBSERVATIONS
CONNECTING OPPORTUNITIES
A, B, C, D
INTERPRET PROBLEMS

38. COMMUNICATE OBSERVATIONS
CONNECTING OPPORTUNITIES
A, B, C, D A, B, C, D
INTERPRET PROBLEMS

39. COMMUNICATE OBSERVATIONS
INTERPRET PROBLEMS
CONNECTING OPPORTUNITIES
A & B = Problem 1
C & D = Problem 2

40. COMMUNICATE OBSERVATIONS
INTERPRET PROBLEMS
CONNECTING OPPORTUNITIES
Problem

41. COMMUNICATE OBSERVATIONS
INTERPRET PROBLEMS
CONNECTING OPPORTUNITIES
Problem
FEATURE
REQUEST

42. COMMUNICATE OBSERVATIONS
INTERPRET PROBLEMS
CONNECTING OPPORTUNITIES
Problem
FEATURE
REQUEST
IDEAS

43. COMMUNICATE OBSERVATIONS
INTERPRET PROBLEMS
CONNECTING OPPORTUNITIES
Problem
FEATURE
REQUEST
IDEAS
20%
PROJECTS

44. COMMUNICATE OBSERVATIONS
INTERPRET PROBLEMS
CONNECTING OPPORTUNITIES
Problem
FEATURE
REQUEST
IDEAS
20%
PROJECTS
RELATED
PROBLEMS

45. COMMUNICATE OBSERVATIONS
INTERPRET PROBLEMS
CONNECTING OPPORTUNITIES
Problem
FEATURE
REQUEST
IDEAS
20%
PROJECTS
RELATED
PROBLEMS
@MENTION
OTHERS

53. Building a shared
understanding

54. Building a shared
understanding
One Interview At A Time

55. I hate
requirements

57. How Do
You…

58. We Try Not To
How Do
You…

60. As A (User)
I Want (Objective)
So That (Why)

61. As A (User)
I Want (Objective)
So That (Why)

62. As Alana
I Want Plan An Event
So That My Team Can Run Effectively

63. As Alana
I Want Plan An Event
So That My Team Can Run Effectively

64. As Alana
I Want Plan An Event
So That My Team Can Run Effectively
A User
New Add Event Button
They Can Add Events

65. Stories Get Their Name From How
They Should Be Used, Not What
Should Be Written.
JEFF PATTON
Story Mapping (2014)
”
“

67. Individuals and
interactions
over processes
and tools

68. Individuals and
interactions
over processes
and tools
Working
software
over comprehensive
documentation
http://agilemanifesto.org

70. Your agile toolbox

71. Prototypes
Journey Maps
Analytics
Surveys
Videos, Talks And Interviews
Requirements Documents

72. Journey Maps

74. your awesome feature

75. FRICTION
your awesome feature

76. FRICTIONFRICTION
your awesome feature

82. Draw the journey.

83. Requirements
Documentation

84. We Try Not To
How Do
You…

85. But Sometimes
We Do
How Do
You…

88. LinesofCode(million)
17.5
35
52.5
70
W
in
3.1
W
in
N
T
W
in
95
('97)
W
in
98
('00)
W
in
2k
('01)
W
in
XP
('01)
W
in
Vista
('07)
W
in
7
('09)
W
in
8
('13)

89. Vs

90. Vs
Confluence Team Calendars
New product
Confluence Page Layouts
New feature, existing product

91. Vs
• What is our MVP? • What is our MVP?
• What about migration?
• PDF/HTML/Word Export
• Copy/paste
• Email notifications
• Resizing layouts
• …

92. Vs

93. Vs

94. Vs

95. Vs

96. Collective Wisdom
Involve everyone in the team
Traceability
JIRA integration
Centralisation
All project docs in one place

97. Collective Wisdom
Involve everyone in the team
Traceability
JIRA integration
Centralisation
All project docs in one place
http://bit.ly/ProductRequirements

98. …By Understanding The Needs Of
Your Customers You Will Be Able To
Deliver Succinct And Sufficient
Documentation…
SCOTT AMBLER
agilemodeling.org
”
“

100. Persona-driven roadmap,
build better experiences,
improve marketing

101. Persona-driven roadmap,
build better experiences,
improve marketing
opportunities
interpretations
observations
Observations,
interpretations,
opportunities

102. Persona-driven roadmap,
build better experiences,
improve marketing
opportunities
interpretations
observations
Observations,
interpretations,
opportunities
“Agile requirements”:
Build your toolbox

103. Defining the
problem
Building the
solution
Getting
feedback

104. Building the
solution

107. BEFORE

108. BEFORE
AFTER Spaces People Calendar Create

109. BEFORE
AFTER Spaces People Calendar CreateSpaces

110. Choose carefully.

118. Hero shot

119. One-line pitch

120. Three Pillars

121. Build your box.
Hero Shot
One-Line Pitch
Three Pillars

122. What if we didn’t have any
documentation?

125. 5 months
20,000unique visitors

126. 20,000

127. 20,000
9,000,000+Confluence users

128. Assume you don’t
have release notes

129. Assume you don’t
have release notes
Even if you’ve got a
flashy video of a
good looking guy!

139. Domino effect

140. Build-a-boxDomino effect

141. Build-a-boxDomino effect Assume no docs

142. Defining the
problem
Building the
solution
Getting
feedback

143. Getting
feedback

145. Friction

153. FEEDBACK?

154. FEEDBACK?

156. Got Feedback?

161. More to come…

163. ↓ barrier to entry
Avoid login, be contextual, avoid context
switching.

164. ↓ fields
Less fields, reduce required fields.
Automatically populate where possible.
* required
↓ barrier to entry
Avoid login, be contextual, avoid context
switching.

165. ↓ fields
Less fields, reduce required fields.
Automatically populate where possible.
* required
Easily express yourself
Quick and simple
Rate this feature:
bad
good
great
↓ barrier to entry
Avoid login, be contextual, avoid context
switching.

167. fake it
‘till you
make it

170. http://developer.atlassian.com/design

174. fake it
‘till you
make it

175. fake it
‘till you
make it
SAVE
$$$
SAVE
TIME
RIGHT
THING

177. Reduce friction

178. Reduce friction
Fake it ‘till you
make it

180. http://bit.ly/AgileFeedbackLoops

181. Defining the
problem
Building the
solution
Getting
feedback

182. Questions?
!
@sherifmansour
sherif@atlassian.com