Read “INSPIRED”

Read INSPIRED: How to Create Tech Products Customers Love.

A product owner heavily talked roles based on this book. Thus, I also read this book to understand him and make easy to communicate with high context.

My impression of the book is excellent to learn definitions of each role to develop products. Of course, we can read the definition of “product owner”, for example. Sometimes, it follows Agile development, but not only that.

The most significant sections is chapter 64, personally. In the chapter, we can read good product team and bad one. Sharing their vision, working as a team, for example. I’d like to recommend the book to colleagues if they haven’t read this yet.

Of course, without doing it, it finishes only reading it. We must practice going the way as a team. So, after reading this book, we must work by ourselves.

One more interesting thing. In this book, we can see “test” techniques or other test related topic include automation. This book isn’t for QA/testers. So, the automation isn’t a difficult one. But, I was glad to see this book mentioned not only user/usability testing but also how important to automate test cases.

Last, from Chapter 66. Top reasons for loss of velocity.

1. Technical Debt
2. Lack of strong product managers
3. Lack of delivery management
4. Infrequent release cycles
5. Lack of product vision and strategy
6. Lack of co-located, durable product teams
7. Not including engineers early enough during product discovery
8. Not utilizing product design in discovery and instead having them try to do their work at the same time the engineers are trying to build
9. Changing priorities
10. A consensus culture

Have a great and enjoy product development for users!