#atlassian
Governing JIRA at Scale 
JORDAN DEA-MATTSON • CHEF DE CUISINE • YAHOO
Lessons Learned 
Flexibility Costs 
Setting Expectations Expect to Automate
Just because you 
can configure JIRA 
every which way, 
doesn’t mean you 
should.
Most JIRA 
instances just 
grew
Where “Just Grew” looks like this!
This makes them 
hard to manage, 
automate and 
upgrade
These costs never 
decrease or end
Lessons Learned 
Flexibility Costs 
Setting Expectations 
Expect to Automate
Don’t advertise 
anything that is 
difficult to manage
The Unreachable 
Utopia: 
Just one 
of every JIRA 
scheme
Not everyone 
will be happy!
Democracy is the worst form of government 
except all those other forms that have been 
tried 
” 
Winston Churchill 
“
Define your 
process for 
making changes 
to JIRA 
in JIRA
Is Easier to Edit 
than to Create
Is Easier to Add 
than to Remove
Start Small 
and 
Grow As Required
Lessons Learned 
Flexibility Costs Setting Expections 
Expect to Automate
Yahoo Tools 
supports 
the 
whole company
We have 
finite time 
and 
finite resources
So we automate 
everything.
But be careful!
Special cases tend 
to break 
automation
We are all special cases 
Albert Camus 
” 
“
No, we don’t want 
any special cases
Consistency is 
what lets you 
govern JIRA at 
scale
Our Conclusions
KISS is good. 
We like KISS.
But KICS is better 
“Consistent”
Thank you! 
JORDAN DEA-MATTSON • CHEF DE CUISINE • YAHOO
I’m Jordan Dea-Mattson and I’ve introduced JIRA into five organizations. 
I’ve also worked with Matt Doar and ServiceRocket for years as well. 
They’ve introduced JIRA into hundreds of organizations 
But I’m here to talk about my sixth one. This time it’s for Yahoo. 
So how big is Yahoo these days? Big! 
We have many different tools and many integrations between them 
We’ve learned much from running the world’s largest Bugzilla instance (7M issues)

Governing JIRA at Scale - Jordan Dea-Mattson