JIRA Software is an extremely flexible and powerful tool, which can be used in a variety of ways. As a 9-year Atlassian veteran, Nick Pellow will outline the innovative ways JIRA Software is being used within Atlassian, and what features our teams find most useful to enhance their processes. I'll cover practical tips, such as how we run Scrum and Kanban, and how we've customized projects and boards to best plan, track, and ship software with the precision of a black-belt judo master. Nick Pellow, Development Manager JIRA Software, Atlassian

1. Black belt tips
for JIRA Software
NICK PELLOW | DEV MANAGER | @NIICK

2. Photo of the JIRA Software Team

3. Esther Asenjo
Atlassian Purchasing
Andy Drizen
JIRA Cloud Mobile
Michael Tokar
JIRA
Edward Zhang
JIRA Service Desk

4. Some assumptions first

5. A software team

6. You’ve worked with
JIRA Software
before

7. Some form of ‘Agile’
team

8. Before we begin

9. Identify risks early with a pre-mortem

11. Esther Asenjo
Atlassian Purchasing
Andy Drizen
JIRA Cloud Mobile
Michael Tokar
JIRA
Edward Zhang
JIRA Service Desk

12. Esther Asenjo
Team lead

13. Separate estimation from planning

14. Time to go into detail
Separate estimation session
Identify blockersFocused

15. Photo of team doing
planning. Someone is
looking out the
window, bored

17. Epics and quick filters to focus the content

18. Voiceover
points only
Point 1
Point 2
Point 3
Point 4
Epic panel

19. Voiceover
points only
Point 1
Point 2
Point 3
Point 4
Click to filter

20. Talking point
Supporting text should be brief
and no longer than 4 lines. Limit one
talking point and image per slide.

21. Voiceover
points only
Point 1
Point 2
Point 3
Point 4
Quick filters

22. “Story Points” is EMPTY
Status in ("To Do", "Ready for Dev”)
labels = squirtle-squad
Quick filter JQL
Unestimated
Not Started
Sub team

23. Voiceover
points only
Point 1
Point 2
Point 3
Point 4
Issue detail
panel

24. Customise your board’s issue detail view

26. Photo of the meeting
with someone saying
that we need a new
issue

27. Voiceover
points only
Point 1
Point 2
Point 3
Point 4
Create issue

28. Voiceover
points only
Point 1
Point 2
Point 3
Point 4
Create issue in
epic

29. Inline issue create

30. Voiceover
points only
Point 1
Point 2
Point 3
Point 4
Create issue
inline

33. Epic
Label
Sprint
Version
Component
And more..Project
Assignee
Populates fields based on filters

34. The keyboard shortcuts to success

35. Assign Assign to me Send top Send bottom
Key shortcuts
+ +

36. Use the dot

37. The dot dialog

38. Photo of team
interested and
engaged

39. Esther Asenjo
Atlassian Purchasing
Andy Drizen
JIRA Cloud Mobile
Michael Tokar
JIRA
Edward Zhang
JIRA Service Desk

40. Andy Drizen
JIRA Mobile

41. Estimation
SO KEEP IT FRESH!
PLANNING POKER
SOME > NONE
Sometimes so hard, plenty of teams
skip it entirely…
Can often seem very arbitrary.
Hard to calibrate a team on story
points
Low engagement == low
commitment

42. Relative estimation

43. Order cards
Planning prep
Assign story pointsPlanning prep
Rough set of stories
for sprint.
Prints the agile cards.
From simplest to most
complex
Start with simplest
set: 1s
Then next simplest
set: 3s, etc etc

45. Blank with title

46. Blank with title

47. Blank with title
SIMPLE
COMPLEX

48. Blank with title

49. Blank with title

50. Blank with title

51. Blank with title

52. Blank with title

53. Blank with titleNew story!

54. Blank with title
1s

55. Blank with title
1s
3s

56. Blank with title
1s
3s
5s

57. Blank with title
1s
3s
5s
8s
13s?

58. Blank with title
3s
1s
5s
8s

59. Some > none
The art of estimation itself
is often the value, not the
estimate.
More
involvement
Tangible cards on the
table is fun. No laptops!
Easier to
estimate
Much faster comparing 2
stories, than all stories!
Relative Estimations

60. Esther Asenjo
Atlassian Purchasing
Andy Drizen
JIRA Cloud Mobile
Michael Tokar
JIRA
Edward Zhang
JIRA Service Desk

61. Michael Tokar
JIRA Platform
“Tokes”

62. Automated workflow triggers

64. Use an open
workflow
Issues can move to
any status

65. ADDING THE TRIGGER

66. TRIGGERS
Branch created
Pull request
merged
Deployment
successful
Type your annotation here,
the dotted line can be
moved and/or re-sized.

67. TRIGGERS
Branch created
Pull request
merged
Deployment
successful
Type your annotation here,
the dotted line can be
moved and/or re-sized.

68. Branch naming conventions

69. feature/JSW-3429_editable_issue_details
<prefix>/<issue-key>_<description>

71. TRIGGERS
Branch created
Pull request
merged
Deployment
successful
Type your annotation here,
the dotted line can be
moved and/or re-sized.

72. DONE means
deployed
On pull request merged
‘Awaiting
deployment’ as a
holding ground
Master means
customers

73. TRIGGERS
Branch created
Pull request
merged
Deployment
successful
Type your annotation here,
the dotted line can be
moved and/or re-sized.

74. Headline 3
Subtext type size is
optimized at 36 pt.
Rehearse
Rely on rehearsing
your voiceover rather
than writing.
Branch
created
No worries
It’s OK if the subtext
lengths differ.
Pull request
merged
Deployment
successful
Branch
created

75. One pull request per issue

76. Progress
>> perfection
Perfection is not
necessary to make an
impact
Each team is
different
Find what works for you
Experiment
Introduce slowly, allow for
critique
Triggers

77. Esther Asenjo
Atlassian Purchasing
Andy Drizen
JIRA Cloud Mobile
Michael Tokar
JIRA
Edward Zhang
JIRA Service Desk

78. JIRA Service Desk
Ed Zhang

79. Lack of progress
Lack of focus
Quality of demos
Sprints are
tough…
Are we there yet ?
Many, unrelated streams of work in
flight
Bad reflection on the team
Bad vibe in the team

80. Sprint goals

81. Demo driven
Sprint goals
MeasurableDecide as a team
With input from PM,
however team needs
buy-in & commitment
During pre-planning,
imagine what the
demo will be like
Be specific.
Build your
measurement first!

82. D3 conversion demoable and
the dashboard performance
improved by 10% on 9 August
ServiceDesk #SprintGOAL

83. Build measurement first

85. Can be used
as pro/con,
hypothesis/
finding, etc.
Use when
explaining
two sides of
a point.
ONE SIDE THE OTHER SIDE

86. Can be used
as pro/con,
hypothesis/
finding, etc.
Use when
explaining
two sides of
a point.
ONE SIDE THE OTHER SIDE

87. Can be used
as pro/con,
hypothesis/
finding, etc.
Use when
explaining
two sides of
a point.
ONE SIDE THE OTHER SIDE

88. Applause

89. Standups!

90. Task centric standups

91. Blank with title

92. Blank with title

93. Blank with title

94. Blank with title

96. Build a standup board

97. Blank with title

98. Blank with title

99. Blank with title

100. Participants
only
Only active participants
will talk
Less waffle
Use this time wisely to
discuss what’s important -
the actual work!
Leaner
“Cut our standup time in
half!”
Task centric standups

101. Black Belt tips for JIRA Software
Separate estimation sessions
Epics and quick filters
Create issues inline
Automatic workflow triggers
Use the dot
Relative estimation
Sprint goals
Task centric standups

102. Applause

103. Bonus JQL Quiz!
JIRA Query Language is the key to JIRA mastery

104. In which version of JIRA was JQL
introduced?

105. 4.0

106. What JQL allows you to find all issues
created in the past 2 weeks?

107. created > -14d

108. Find all issues in an open sprint?

109. Sprint in openSprints()

110. Select all issues where the label ‘foo’ does
NOT exist?

111. Blank with title

112. labels != “foo” OR labels is EMPTY

113. Show all issues referencing a Pull Request
that is still open?

114. development[pullrequests].open > 0

115. Thank you
NICK PELLOW | DEV MANAGER | @NIICK