Covering a very wide spectrum of software team related issues from distributed remote team participation to architecture, to project control and team building.
This great book is highly relevant and useful in my team lead and architect roles yesterday, today, and I am 100% sure tomorrow also!
James Coplien is quite an interesting guy. I've read a bunch of his essays in the past which have been quite enlightening. You can find them on
"Cope's" web site.
Why I recommend Organizational Patterns of Agile Software Development:
Reason 1: It is based on a great deal of research which looks to be scientifically thought out, hypotheses were created, samples statistically selected and information collected and then analysed carefully. So its fairly safe to refer to it and the cases/patterns mentioned that worked or failed.
Reason 2: In my studies of Organisation Behaviour, Industrial Psychology, Business Management and Human Resource Management, there were a number of consistent themes that were delved into deeply in this book, which has a great deal of real world emphasis and quick illumination, whereas the theory texts are more verbose and not as readily applied.
Reason 3: It is also consistent with my past experiences of organisation behaviours that were dysfunctional as well as those cases where organisations were extremely functional.
Reason 4: Like the Gang of Four's Design Patterns, this book now somehow "lives" in the back of my mind (knowledge was deeply absorbed and incorporated into my thinking without
conscious study) so that when I encounter situations I can either more clearly identify what's going wrong, and what possible patterns could be applied, in which possible sequences, in order to address the problem(s), or simply refer to this reference book and delve deeper into the issues and solutions effectively and efficiently.
Reason 5: People I have already referred it to have come back to me and been as astonished by it.
Thankyou for supporting!
