Chapter 2

If every bug is urgent, which one really is?

Lỗi nào cũng khẩn, vậy lỗi nào thật sự khẩn?

The chapter's question

What severity is this bug, and what response does that severity require?

Big idea

A shared severity scale helps the whole company respond at the right size.

In this chapter

  1. Part 2.1

    Defining Each Level

    Is my severity scale based on the number of people affected or the level of damage?

  2. Part 2.2

    Lost Money, Lost Data

    Where do bugs that cost users money or data rank?

  3. Part 2.3

    Small but Widespread

    Is a small bug hitting every user worse than a big bug hitting a few?

  4. Part 2.4

    Raising or Lowering Severity

    Who may change an incident's severity?

The reading for this chapter is inside Conan School

This chapter has 4 readings, with case stories and exercises. Chapter 1 of The Cost of a Bug is free to read right here.

Read in Conan School

Chapters of The Cost of a Bug

  1. 1.When the product breaks, what does the PM do?
  2. 2.If every bug is urgent, which one really is?
  3. 3.Does a longer bug list mean a better product?
  4. 4.Does finding someone to blame mean fewer mistakes?
  5. 5.Who decides what's good enough to ship?