At Atlassian, we’ve been dog-fooding Jira since the beginning of time. This means we get to use every feature and improvement firsthand before it gets delivered to you. Building the new Jira, this posed an interesting challenge – we had to get everyone moving to the new experience. In this talk, we’ll take you through our journey of getting everyone on-board onto new Jira. There will be a guided tour on how to best use the new Jira for the full cycle of product development. By the end of this session, you’ll know how to make new Jira work for your team and not the other way round.

1. Ultimate Dogfooding: Behind the
scenes of building the new Jira
ERIKA SA | PRODUCT MANAGER | ATLASSIAN | @ESA
JAMES ROTANSON | PRODUCT DESIGNER | ATLASSIAN | @JROTANSON

3. Dogfooding
Internal beta

4. Dogfooding
Internal beta

5. SearchProjects Create
Backlog
Agile board
Releases
Reports
All issues
Components
Add-ons
Confluence Team Hipchat Room
Space Station Dev Roadmap
Teams in Space Org Chart
Orbital Spotify Playlist
Hyperspeed Bitbucket Repo
Add shortcut
PROJECT SHORTCUTS
Software Project
Jira team
Jira board
QUICK FILTERS: Critical partners Only my partners Recently updated
DW-342
Layouts usability test
Navigation
DW-390
SWIFT UI exploration
Settings
DW-405
Fields spec - Priority
Settings
DW-262
Blog about how to best
use Jira for designers
DW-293
Usage pattern on multi-
line field / long text field
12 To do
DW-292
Update an assignee
Settings
DW-345
Worklow spec - edit
View issue
DW-345
Show more custom fields
View issue
3 Exploring
DW-123
Terminology testing
Settings
DW-345
Project settings nav
Navigation
2 Active research
DW-123
Analytics on terminology
View issue
1 Analysing
Label NoneGROUP BY
Jira board
✨
DW-345
Workflow spec - Editing transition
DW-96
Fields spec - Show more custom
fields
DW-292
Rule 3: Update an assignee
EXPLORING
!
3 MAX: 10
DW-345
Project settings - navigation test
DW-123
Terminology testing - issues
ACTIVE RESEARCH
#
2
DW-123
Analytics on terminology
ANALYSING
"
1
DW-342
Layouts usability test
DW-390
SWIFT UI exploration
DW-405
Fields spec - Priority
DW-262
Blog about how to best use Jira
for designers
DW-293
Usage pattern on multi-line field /
long text field
BACKLOG 24

6. SearchProjects Create
Jira board
QUICK FILTERS: Critical partners Only my partners Recently updated
DW-342
Layouts usability test
Navigation
DW-390
SWIFT UI exploration
Settings
DW-405
Fields spec - Priority
Settings
DW-262
Blog about how to best
use Jira for designers
DW-293
Usage pattern on multi-
line field / long text field
12 To do
DW-292
Update an assignee
Settings
DW-345
Worklow spec - edit
View issue
DW-345
Show more custom fields
View issue
3 Exploring
DW-123
Terminology testing
Settings
DW-345
Project settings nav
Navigation
2 Active research
DW-123
Analytics on terminology
View issue
1 Analysing
Give feedback
Learn more
Project settings
Add item
Board
Roadmap
Software Project
Jira team
Label NoneGROUP BY
Jira board
✨
DW-345
Workflow spec - Editing transition
DW-96
Fields spec - Show more custom
fields
DW-292
Rule 3: Update an assignee
EXPLORING
!
3 MAX: 10
DW-345
Project settings - navigation test
DW-123
Terminology testing - issues
ACTIVE RESEARCH
#
2
DW-123
Analytics on terminology
ANALYSING
"
1
DW-342
Layouts usability test
DW-390
SWIFT UI exploration
DW-405
Fields spec - Priority
DW-262
Blog about how to best use Jira
for designers
DW-293
Usage pattern on multi-line field /
long text field
BACKLOG 24

7. Get everyone
onboard
Explain benefits
Adapt old practicesDiscover new practices
Move instances Roll out
CHANGE IS NOT ALWAYS EASY
NEW JIRA

8. 3 key points
Be open to change
Allow autonomy & have fun
Let it grow
Make iterative improvement
Put in practice
Go deep and make Jira work
for your team

9. 3 key points
Be open to change
Allow autonomy & have fun
Let it grow
Make iterative improvement
Put in practice
Go deep and make Jira work
for your team

10. 3 key points
Be open to change
Allow autonomy & have fun
Put in practice
Go deep and make Jira work
for your team
Let it grow
Make iterative improvement

11. 3 key points
Be open to change
Allow autonomy & have fun
Put in practice
Go deep and make Jira work
for your team
Let it grow
Make iterative improvement

12. 1. Be open to
change
Put in practice
Go deep and make Jira work
for your team
Let it grow
Make iterative improvement

13. Jira is opinionated
and you have to
get it right from
the start
IN THE PAST

15. FIELD
CONFIGURATION
ISSUES
SCHEMES
EPIC
SPRINT

16. FIELD
CONFIGURATION
SCHEMES
ISSUE TYPE
SCREEN SCHEME
EPIC

18. Next-gen project

19. Independent, open by default

20. I’d like to challenge
every person in the
team to create a
project that they will
use in their lives.
Ed Zhang
Developer Team Lead, Jira

21. Some interesting use cases

23. ED’S GAMING PROJECT
Track games
All kinds of games from
different type of
platforms
Card preview
Images on cards for
easy recognition

24. ED’S GAMING PROJECT
Issue types
Different types of
console or gaming
platform
Fields
configuration
- Completion target
(Dropdown)
- How long to beat
(Time)

25. ED’S GAMING PROJECT
Custom
issue types
Different types of console or
gaming platform through issue
type configuration

26. ED’S GAMING PROJECT
Drag and drop
custom fields
- Completion target (Dropdown)
- How long to beat (Time)

28. ROTO’S ART EXHIBITION
Track artworks
Personal gallery exhibition.
Landmarks of Sydney and
Japan.
Stages
- To do
- Ideas
- Making
- Printing
- Done

29. ROTO’S ART EXHIBITION
Roadmap
Planning and scheduling
towards the event

30. ROTO’S ART EXHIBITION
Streams
- Artworks
- Printing
- Equipments
- Marketing
- Budget
- Events

32. JIRA CLOUD CAMP PLANNING
Event planning
Internal conference on
sharing knowledge &
best practices across
different Jira teams.

33. JIRA CLOUD CAMP PLANNING
Track talk ideas
Everyone is open to
submitting ideas.

34. JIRA CLOUD CAMP PLANNING
Track talk ideas
Everyone is open to
submitting ideas.

35. JIRA CLOUD CAMP PLANNING
Upvote custom field
Everyone in the board can vote by
putting their names for the talk idea.
[Roto]

36. Play, as a team
Collaborative process, lots of
excitement, no consequenceses.
Rigid process
Fear of breaking something and it’s for
work only

37. Ownership
Each team or individual owns the
process. There is a sense of identity. This
was unexpected.
It’s just work..
Don’t think we would’ve gotten to here if
it’s for tracking day to day job things

38. Learning by doing
Experiment with what use case fits in to
the daily usage.
Learning by docs
Mostly through googling, asking around

39. It was scary, but opening
up has made it a liveable
place where we can get
actual work done.

40. OUR
CHALLENGE
WHAT ABOUT
YOUR TEAM?

41. 3 key points
Be open to change
Allow autonomy & have fun
Let it grow
Make iterative improvement
Put in practice
Go deep and make Jira work
for your team

42. 3 key points
Be open to change
Allow autonomy & have fun
Put in practice
Go deep and make Jira work
for your team
Let it grow
Make iterative improvement

43. 3 key points
Be open to change
Allow autonomy & have fun
2. Put in practice
Let it grow
Make iterative improvement

44. Design
Product
Development

45. Reach Alignment
Know why we are doing
what we are doing.
Customer Insights
Learn as we ship and
communicating insights.
Ensure Quality
Fill in each other’s blindspots.
Get multiple perspective on
the same problem.
How we use Jira to…

46. Alignment
Know why we are doing what
we are doing.
Common
goals
Alignment
Quality
Visibility

47. The single biggest problem
in communication
GEORGE BERNARD SHAW (THE NOBEL PRIZE IN LIT)
is the illusion it has taken
place

49. Issue types
Bug
Story
Design
Spec
Research
Analytics
Others

53. ALIGNMENT
One source of truth
See progress on dev work, but
also the research and spec
Tracking over time
See history, and why certain
decisions are made at a point in
time.

54. Quality
Excellence from concept to
launch.
Common
goals
Alignment
Quality
Visibility

55. Designers
Ideal vision, big picture,
happy paths
Developers
Execution, implementation
details, edge case
The gap in between

58. Designers 🙌 Developers
Develop empathy through rich integration

59. Customer Insights
Learn as we ship and
communicate insights
Common
goals
Alignment
Quality
Insights

64. Consistent themes
over time?

65. Consistent themes
over time?

66. 3 key points
Be open to change
Allow autonomy & have fun
Put in practice
Go deep and make Jira work
for your team
Let it grow
Make iterative improvement

67. 3 key points
Be open to change
Allow autonomy & have fun
Put in practice
Go deep and make Jira work
for your team
Let it grow
Make iterative improvement

68. 3 key points
Be open to change
Allow autonomy & have fun
Put in practice
Go deep and make Jira work
for your team
3. Let it grow

69. Our process didn’t
look like this from
day 1
BACK IN TIME

72. YOUR TEAM PRACTICES WILL
GROW OVER TIME.
NO TWO TEAMS USES JIRA THE
SAME WAY.

73. Bring into the journey
Early, frequent engagement
makes it easier for everyone
to align.
Continuous feedback
Your team should be
empowered to make decisions
and provide feedback
Keep in mind

74. Reduce repetitive work
EXAMPLE 1

76. Why do I have to assign
myself to content review
every time?
SAM, LEAD CONTENT DESIGNER

78. Capture relevant information
EXAMPLE 2

80. Why can’t I fill the
interview time in a more
consistent way?
ASHLEIGH, MANAGER

82. Embrace ways of working
EXAMPLE 3

83. Scrum is too restrictive,
how can we move faster?
CHRISTOPHER, DEVELOPER TEAM LEAD

86. 3 key points
Be open to change
Allow autonomy & have fun
Let it grow
Make iterative improvement
Put in practice
Go deep and make Jira work
for your team

87. What’s your story?

88. Thank you!
ERIKA SA | PRODUCT MANAGER | ATLASSIAN | @SOCIALMEDIAHANDLE
JAMES ROTANSON | PRODUCT DESIGNER | ATLASSIAN | @JROTANSON