Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

How to avoid getting lumped with the tickets that take forev

No description
by

Greg Baker

on 26 November 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of How to avoid getting lumped with the tickets that take forev

That's just a collection of Bayesian classifiers!
How long is it going to take?
What else did the robots find?
Conclusion
Please install AEED in your JIRA instance.

Did I tell you it's free at the moment?
Why I started researching JIRA tickets
A large customer of mine had a lot of re-assigned tickets
1 in every 6 tickets was handed over to someone else
If a ticket is re-assigned before, there was a 50% chance that it will be re-assigned again.
This customer was not using JIRA, by the way
Successful Change tickets and their approvers
Google
Predict
Unsuccessful Change tickets and their approvers
Incomplete Change
Change tickets were being approved by the wrong teams
How to avoid getting stuck with tickets that take a long time to resolve
The easier problem
Approver List
I could have just sent emails to all their tech staff
and let their SPAM filters handle it.
What was it actually filtering on?
How was that working?
I rewrote it.
It's called AEED
It works with JIRA
It's free (at the moment)
Hand-crafted algorithms
4 - 10 working days per re-assignment
Who is Dr Robin Dunbar?
Dunbar's number
You can only keep track of about 150 people.
Greg's corollary: if you could assign a ticket to any one of 150 people, you'll get it wrong.
So will everyone else.
And you will need to spend time to confirm that a ticket really isn't your responsibility.
So that you can then hand it over to the wrong person as well.
4-10 working days per reassignment
OK
I've got no idea.
Robots assign more accurately than humans
At least
40%
of variation in ticket closure time can be predicted
"MEETING"
8 standard deviations away from the duration of other tickets
(Clearly not a Gaussian distribution)
Wednesday afternoon
Matty Mariansky
(Meekan Scheduling Robot)

We do see more scheduling activity at Meekan towards the second half of the week (Wed+Thu).

[...] Often times, just the horror of having to arrange a meeting leads to procrastinating it, when in fact it could be done automatically in a few seconds
Customer-specific stuff
Assignee
Product name
"Chemical Tank"
"Implement"
Some other time of day
Non-tech
: Help, I need this fixed.
Tech
: If I were doing it, I would ___ the ___. But the right approach is to get the ___ team to ___ the ___.
Non-tech
: How long will that take?
Greg Baker (gregb@ifost.org.au)
http://www.ifost.org.au/aeed
Full transcript