Top positive review
27 people found this helpful
A paradigm shift in software development
on 20 December 2002
5 stars to the writers, less of them to the publisher (you don't get to see graphics that bad these days). I read 'Extreme Programming Explained' almost two years ago, enjoyed it, and changed some of my views on the development process; I adopted some practices, but the XP Planning Game did not fit in our process. I the read 'Agile Software Development Ecosystems', enjoyed it, and learned that XP was not the only alternative to the conventional software development process. Now, Scrum, and its well thought simplicity, has shown me a proven and understandable way to manage software projects, and deepened the changes that the XP book stared on me.
The discussion on the "defined process control model" vs the "empirical process control model", in Chapter 2 and available on line, should be mandatory reading for any one involved with IT. Chapter 5 extends this discussion and is also outstanding.
Chapter 6 provides several models/views to explain Scrum; having several models of the same thing is something that you do very often when doing software design and deepens your understanding of the system; I liked the use of this technique in prose and the very interesting models covered.
Read it. You may not want to become a Scrum practitioner, but the book will probably change the way that you think about software development.