I read Kaizen Journey and wanted to jot down my thoughts.

Thoughts

I had the impression that the story format was both easy and difficult to read, but upon finishing, I felt it was a clear way to experience the concept of "crossing boundaries."

The Agile practices presented in the book were not new to me, as I had learned about them elsewhere.

However, what stood out in this book was the strong message regarding the purpose and significance of "crossing boundaries," rather than the details of those practices.

Reflecting on my own experiences, I have thought about what kind of Kaizen is necessary for a team to enhance its results beyond its own boundaries and contribute to the organization.

I feel that "crossing boundaries" is an important keyword in the pursuit of outcomes in software projects, whether it’s about achieving greater results, delivering results faster, or making it easier to achieve results.

I believe this book addresses themes such as how to expand the field of value delivery from individuals to teams and from teams to the entire organization, and how to improve development through process enhancements.

I read this book without any prior knowledge, but it might have been easier to read if I had looked at the Appendix first.

The story in this book is set in a contract development company, but I think those with experience in business companies might find the content resonates more with them. (I might be mixing in my own biases and prejudices based on my experiences...)

So, I wonder if Sodekawara could have collaborated with Ejima and the others from the very beginning! Haha.