Page XXXV:

Page XL:


Page 28:

Page 32:

Page 44:

Page 56:

Page 76:

Page 82:

Page 90:

Page 107:

Page 122:

Page 133:

Page 142:

Page 150:

Page 157:

A small, cross-functional team led by a product owner orchestrates product discovery work.

Page 162:

Page 170:

Page 181:

Discovery isn’t about building software

Discovery work isn’t about building shippable software. It’s about learning. It’s about building a deeper understanding of what we could build. It’s about asking and answering questions like:

  • What problems are we really solving?
  • What solutions could be valuable to our organization and to customers buying or adopting the product?
  • What does a usable solution look like?
  • What’s feasible to build given the time and tools that we have?

Page 198:

Prioritize specific business goals, customers, and users, and then their goals, before priortiziing features.

Page 202: