Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?

Bugs and Priority

Reading: https://hackernoon.com/bugs-priority-3b5cf5f6aadd#.6dea1eo0d

Intro

  • Maintaining software is about tradeoffs
  • Shared understanding of tradeoffs is important
  • Tracking bugs is important
  • What priority means?
  • What else should we be using?

Problems

Opaque

  • Depends on the person prioritizing
    • I disagree, I think many times there are standards for our priorities
  • Seems to make the assumption that there is one person setting priority on tasks…not really “at scale”

Not fixed

  • But…it is most of the time….
  • How do we get everyone on the same page?

Standardizing

What kind of defect

  • e.g., crash/data loss/cosmetic

What is the frequency of that defect?

  • Is it happening all the time?
  • Is it happening at a very low rate?

Chart

  • Understanding variables key to standardizing decisions
  • Chart for each company is different, only important that people agree
  • Process should be flexible enough to break from time-to-time

Final thoughts

  • Structured data around what kind of defects you have
  • Let’s you build reporting in your bug tracker
  • More informed about trade-offs

Thcipriani final notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment