Driving JIRA Adoption Through Simple Configuration
-
Upload
atlassian -
Category
Technology
-
view
1.472 -
download
0
Transcript of Driving JIRA Adoption Through Simple Configuration
DORIAN KERSCH • SCRUMMASTER • INTUIT • @DORIANKERSCH
Driving JIRA Adoptionthrough simple configuration
K EY A G I L E PR A C T I C ES
IN T U IT A GIL E
T A K EA WA YS
Agenda
Intuit Confidential and Proprietary4
”Deliver world-class agility through enterprise-wide adoption of Agile principles”
Key Agile Practices
Streamlined WorkflowsJIRA PlaybooksAgile Flight Crews Customer Benefit
Key Agile Practices
The Problem• Inconsistent execution• Task vs value ownership• Mini waterfall bottlenecks
The specific team members needed to deliver a story
Agile Flight Crews
Cross functional story team
Agile Flight Crews
Story Huddle
Checklist
All the people required regardless of skillset.
Flight crew prepares story for execution (Definition of Ready, Tasks)
Ensuring consistent high quality execution every story
The Problem• Aligning tools with Intuit Agile• 100s of individual configurations• Unable to collect consistent
metrics
JIRA Playbooks
How Intuit scales JIRA configurations
One Base “Template”
JIRA Playbooks
Extend by business unit or team structures
Avoid “one” offs
Define the company standard. Keep it bare bones.
Its okay to have some variations.
Jira isn’t always the answer to the problem. Work with the teams.
Preferred: Intuit Base Config
Screens
Fields
Workflows
Approved Option: Example
Business Unit A Config:
Intuit Base Config
Issue Type + “Sub-task”
Fields + “Country”
Workflow + “Verify”
Deprecated: All other configs
Required: Business Unit or Intuit Config
Permissions
Notifications
Issue types
Focus on customer benefit
• Understand the customer problem and solve for it.
• Incremental delivery of value
• No easy way to validate success
• Big bang releases• Didn’t prioritize most valuable
customer features
The Problem
Business Value Field
Focus on Customer Benefit
Success Metric Field
Track at story, epic or initiative level.
What does success look like?
The Problem• Too many fields, too much overhead• Focused on work not value• Cross-team status was complicated
Simplified Workflow
• Simple workflows that get more complex with automation
Create a basic
Streamlined Workflows
Limit Required up-front
Automate
Start simple. Learn from customers. Expand through automation and business needs
Keep create screens simple. Require via transitions as you go through the flow.
Keep customers doing their work and JIRA reflects their work.
Takeaways
Allow FlexibilityKISS Automate
KISS, Flex, Automate
Do the simplest possible thing
effectively.
But not chaos If it can be automated, Automate it.
Thank you!
DORIAN KERSCH• SCRUMMASTER • INTUIT • @DORIANKERSCH