Chapter 5

Who decides what's good enough to ship?

Ai quyết định thế nào là đủ tốt để phát hành?

The chapter's question

Has my team agreed what level of quality is enough to release?

Big idea

The quality bar is a product person's choice, whether or not they say it out loud.

In this chapter

  1. Part 5.1

    Release Criteria

    Which conditions are mandatory before a release ships?

  2. Part 5.2

    Gradual Rollouts

    Does releasing to a share of users first reduce the damage from bugs?

  3. Part 5.3

    The Rollback Path

    If the new release breaks, how long does rolling back take?

  4. Part 5.4

    Counting Incidents per Quarter

    What does this quarter's incident count compared with last quarter's tell me?

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?