|||
I used to do book summaries, writing a short snippet about each book I read and publish them. However, I found them to be tedious and am not sure it really add any value to your life or mine! Even when I summarised them in groups, it didn’t seem to have improved either of our experience. It was still a tedious documentation exercise. It wasn’t until i reread about agile methodology that i realise why this manner of documenting my reading is not very useful. So instead of “book summaries”, it’s now a message, like no more dieting.
Have you been doing something over and over again, but haven’t understood why you’re really doing it? Try questioning the value for it by asking 2 simple questions:
Although I have been in agile organisations for a number of years, it’s only recently that I started thinking more deeply into what being agile means. In particular, on the notion of documentation for the sake of documentation, vs honing that documentation to be fit for purpose, in this case, writing for a reader like me.
I hope this change in purpose will lend to much better writing than mere reporting about a book. I’m sure the better writers out there have figured this out. I am just glad that I manage to figure this out now. Better late than never!
