Inside JIRA Bug Processes: JIRA Best Practices

39

description

 

Transcript of Inside JIRA Bug Processes: JIRA Best Practices

Page 1: Inside JIRA Bug Processes: JIRA Best Practices
Page 2: Inside JIRA Bug Processes: JIRA Best Practices

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

Page 3: Inside JIRA Bug Processes: JIRA Best Practices

• JIRA’s triage process

• JIRA’s warranty bug process

• How we prioritize bugs

• JIRA’s QA processes

• JIRA’s workflow

Overview

Page 4: Inside JIRA Bug Processes: JIRA Best Practices

Bugmaster: a single developer responsible for the management of bugs

Page 5: Inside JIRA Bug Processes: JIRA Best Practices

• An error producing an unintended effect

A bug

Page 6: Inside JIRA Bug Processes: JIRA Best Practices

• An error producing an unintended effect

• After JIRA is released

A bug

Page 7: Inside JIRA Bug Processes: JIRA Best Practices

• An error producing an unintended effect

• After JIRA is released

• Generally excluding poor design

A bug

Page 8: Inside JIRA Bug Processes: JIRA Best Practices

• 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

Page 9: Inside JIRA Bug Processes: JIRA Best Practices

Not quite features; not quite a bugs: fugs.

Page 10: Inside JIRA Bug Processes: JIRA Best Practices
Page 11: Inside JIRA Bug Processes: JIRA Best Practices

• Every day

• All new and updated bugs

• Focus on rapid response

Triage

Page 12: Inside JIRA Bug Processes: JIRA Best Practices
Page 13: Inside JIRA Bug Processes: JIRA Best Practices
Page 14: Inside JIRA Bug Processes: JIRA Best Practices
Page 15: Inside JIRA Bug Processes: JIRA Best Practices

• Components

• The area of the code base affected

• Labels

• The people who care about the issue

• Metadata

Classification

Page 16: Inside JIRA Bug Processes: JIRA Best Practices
Page 17: Inside JIRA Bug Processes: JIRA Best Practices
Page 18: Inside JIRA Bug Processes: JIRA Best Practices

• Conversations

• Customer feedback

• Set expectations

Public tracker

Page 19: Inside JIRA Bug Processes: JIRA Best Practices
Page 20: Inside JIRA Bug Processes: JIRA Best Practices
Page 21: Inside JIRA Bug Processes: JIRA Best Practices

This is affecting us too.”“

Page 22: Inside JIRA Bug Processes: JIRA Best Practices

When will this be fixed?”“

Page 23: Inside JIRA Bug Processes: JIRA Best Practices

If you fix this I will make all

your dreams come true.”“

Page 24: Inside JIRA Bug Processes: JIRA Best Practices

• Faster to fix

• Raises new feature quality

• Developers responsible for quality

• Gives bugfix budget back to feature teams

Warranty bugs

Page 25: Inside JIRA Bug Processes: JIRA Best Practices
Page 26: Inside JIRA Bug Processes: JIRA Best Practices
Page 27: Inside JIRA Bug Processes: JIRA Best Practices

• Keep our goals in mind

Prioritization

Severe customer

impact

Purchase and Upgrade

Creeping normalcy

Affect ing many

customersHigh support costs

Page 28: Inside JIRA Bug Processes: JIRA Best Practices

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

Page 29: Inside JIRA Bug Processes: JIRA Best Practices

Board of Eric

Page 30: Inside JIRA Bug Processes: JIRA Best Practices

• Match fix-rate to demand

• Fix in as few versions as possible

• Balance urgency and efficiency

Work allocation

Page 31: Inside JIRA Bug Processes: JIRA Best Practices

JIRA Agile

Page 32: Inside JIRA Bug Processes: JIRA Best Practices

Swimlanes

Page 33: Inside JIRA Bug Processes: JIRA Best Practices

Cumulative flow

Page 34: Inside JIRA Bug Processes: JIRA Best Practices

JIRA Workflow

Page 35: Inside JIRA Bug Processes: JIRA Best Practices

Feature workflow - an aside

Page 36: Inside JIRA Bug Processes: JIRA Best Practices

JIRA Workflow

Page 37: Inside JIRA Bug Processes: JIRA Best Practices

• 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

Page 38: Inside JIRA Bug Processes: JIRA Best Practices

Thank you!

Er ic Da lg l iesh • J IRA Team Lead • At lass ian • @er icda lg l iesh

Page 39: Inside JIRA Bug Processes: JIRA Best Practices

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