Chapter 5

Are changing requirements really the client's fault?

Yêu cầu đổi liên tục là lỗi của khách hàng sao?

The chapter's question

How do I handle a new request midway through?

Big idea

Changing requirements are normal; changes nobody records are the problem.

In this chapter

  1. Part 5.1

    An Early Prototype

    Do I show users a rough version in the first week?

  2. Part 5.2

    Logging Each Change

    Is every change recorded with a reason and who agreed?

  3. Part 5.3

    Trading Scope

    If this is added, which task is dropped or delayed?

  4. Part 5.4

    Reviewing After Delivery

    A month later, did what I built solve the right problem?

The reading for this chapter is inside Conan School

This chapter has 4 readings, with case stories and exercises. Chapter 1 of Ask the Right Question Before Building is free to read right here.

Read in Conan School

Chapters of Ask the Right Question Before Building

  1. 1.Do they need that feature, or a problem solved?
  2. 2.Is the person asking the one who'll use it?
  3. 3.Does asking what users want reveal what they need?
  4. 4.Everyone nodded in the meeting, but did we agree?
  5. 5.Are changing requirements really the client's fault?