Arrow icon
Ness Labs: Make the most of your mind
Learn more about Joggo

A Summary of

Software Quality, Bugs, and SLAs

by
Rushabh Doshi
View original

Software development is full of defects and evolving infrastructure. Framework to solve quality issues:

Quality

  • Correctness: solve intended problem
  • Performance: latency and speed matter
  • Reliability: avoid crashes and upload failures
  • Craft: create a find-tuned, polished experience

Prioritization

Have a framework to determine how quickly the bug should be addressed: - P0: Bug to be solved now, including services going down or major security defects - P1: Within 24 hours - P2: Within a week - P3: Within two to four weeks - P4: Catchall priority into the next sprint

Continuous improvement

  • Control the number of bugs while continuing to do feature development
  • Set a target of how many SLA violations you allow

Accountability

  • Ensure that leadership and peer functions are involved
Related content
See all posts
Arrow icon
/
Liza Mash Levin
/

The road to Product: How my engineering background got me to product management and the lessons I’ve learned.

Read more
November 28, 2015
/
Lulu Cheng
/

Getting to “technical enough” as a product manager

Read more
/
Rushabh Doshi
/

Software Quality, Bugs, and SLAs

Read more
/
Julie Zhuo
/
Medium

How to Work with Engineers

Read more
October 1, 2018
/
Sachin Rekhi
/
Sachin Rekhi

The Art of Being Compelling as a Product Manager

Read more