This article was originally published on bmf-tech.com.
Kaizen Journey - Here are my thoughts after reading it.
Thoughts
I found the story-like format both easy and difficult to read at times, but by the end, I felt it was an effective way to experience "crossing boundaries."
The Agile practices mentioned in the book were not new to me, as I had learned them elsewhere.
However, this book strongly conveyed the purpose and significance of "crossing boundaries" rather than the details of those practices.
Reflecting on my own experience, there were times when I considered what kind of Kaizen was necessary for a team to exceed its boundaries, improve results, and contribute to the organization.
I feel that "crossing boundaries" is a key concept in pursuing outcomes in software projects, whether it's achieving greater results, achieving them faster, or making it easier to achieve them.
This book addresses themes such as expanding the field of value delivery from an individual to a team, and from a team to the entire organization, and improving development through process improvement.
I read this book without any prior knowledge, but it might have been easier to read if I had looked at the Appendix first.
Although the story is set in a contract development company, I think those with experience in business companies might find the content more relatable. (This might be influenced by my own biases and prejudices...)
So, perhaps Sodegaura-san could have collaborated with Ejima-san and others from the beginning, haha.
Top comments (0)