This book has been my bed time reading for the last couple days. The authors' critics on traditional software development methodology and comment on modeling software development as a dynamic process hit the bull's eye. In fact, back in college, when I was taught the
waterfall approach in software engineering class, I had my doubts: there are just too many uncertainties in the process to make it a static assembly line.
Scrum methodology makes sense because it recognizes and utilizes the dynamics embedded in software development process, instead of trying to control it. I might get
Srumatized some time after I get over with this CFA stuff...
