Post on 23-Jan-2015
description
Er ic Da lg l iesh • J IRA Team Lead • At lass ian • @er icda lg l iesh
Inside JIRA Bug ProcessesAND SOME J IRA BEST PRACTICES
• JIRA’s triage process
• JIRA’s warranty bug process
• How we prioritize bugs
• JIRA’s QA processes
• JIRA’s workflow
Overview
Bugmaster: a single developer responsible for the management of bugs
• An error producing an unintended effect
A bug
• An error producing an unintended effect
• After JIRA is released
A bug
• An error producing an unintended effect
• After JIRA is released
• Generally excluding poor design
A bug
• An error producing an unintended effect
• After JIRA is released
• Generally excluding poor design
• Or anything else we want to call a bug
A bug
Not quite features; not quite a bugs: fugs.
• Every day
• All new and updated bugs
• Focus on rapid response
Triage
• Components
• The area of the code base affected
• Labels
• The people who care about the issue
• Metadata
Classification
• Conversations
• Customer feedback
• Set expectations
Public tracker
This is affecting us too.”“
When will this be fixed?”“
If you fix this I will make all
your dreams come true.”“
• Faster to fix
• Raises new feature quality
• Developers responsible for quality
• Gives bugfix budget back to feature teams
Warranty bugs
• Keep our goals in mind
Prioritization
Severe customer
impact
Purchase and Upgrade
Creeping normalcy
Affect ing many
customersHigh support costs
Alternating theme work
High impact
&
urgent bugs
LDAP
JIRA 5.2.x JIRA 6.0.x JIRA 6.1.x
Search
• Retain some time for urgent work
• Work on themes to tackle hard problems
Board of Eric
• Match fix-rate to demand
• Fix in as few versions as possible
• Balance urgency and efficiency
Work allocation
JIRA Agile
Swimlanes
Cumulative flow
JIRA Workflow
Feature workflow - an aside
JIRA Workflow
• Triage daily
• Know why you’re fixing bugs
• Quality should belong to the developers
• Bug and story processes can differ
• Make it easy to give feedback
• Listen to that feedback
Summary
Thank you!
Er ic Da lg l iesh • J IRA Team Lead • At lass ian • @er icda lg l iesh
Text code below to 22333or visit http://bit.ly/197jucS
Inside JIRA Bug Processes: JIRA Best Practices
To join this session, send text 136888 to
AWESOME = 32
PRETTY GOOD = 31
NOT BAD = 30
MEH = 2Z
Rate this Talk