<< 1 >>
Rating: 
Summary: Thanks Murray for Emphasizing Leadership.
Review: Murray Cantor's book discusses leadership, which is an important, though neglected, area of software development. In the introduction Murray Cantor makes it clear this isn't a 'how to' book about software development -- though he writes well on this here -- but this book is about *leading* a software development process. Again and again Murray reminds us that developing software is a team effort, and that only as an effective team will we succeed.
Murray drives this point home forcefully in chapter 3 when he reminds the reader that software projects are non-linear. He observes, correctly, that "Common sense flows from a shared view of how the world works." On the next page he reinfoces this with his tip that our new common sense approach to development is about leadership. From this point on, Murray illustrates the way in which to apply the team concepts to the process of building software.
If the reader is current with the literature as it pertains to development methods, then the technology in the book will not be new. Nevertheless, the lessons pertaining to team building are as profound as they are necessary. Those using the book as an introduction to development methodology will have the treat of learning this from one of the best, and as a bonus receive his sound advice regarding leadership.
Murray has written a book that should be on the shelf of any manager, er leader, associated with the development of software products. This is definitely a "two-thumbs-up" book.
Rating:
Summary: Thanks Murray for Emphasizing Leadership.
Review: Murray Cantor's book discusses leadership, which is an important, though neglected, area of software development. In the introduction Murray Cantor makes it clear this isn't a 'how to' book about software development -- though he writes well on this here -- but this book is about *leading* a software development process. Again and again Murray reminds us that developing software is a team effort, and that only as an effective team will we succeed.
Murray drives this point home forcefully in chapter 3 when he reminds the reader that software projects are non-linear. He observes, correctly, that "Common sense flows from a shared view of how the world works." On the next page he reinfoces this with his tip that our new common sense approach to development is about leadership. From this point on, Murray illustrates the way in which to apply the team concepts to the process of building software.
If the reader is current with the literature as it pertains to development methods, then the technology in the book will not be new. Nevertheless, the lessons pertaining to team building are as profound as they are necessary. Those using the book as an introduction to development methodology will have the treat of learning this from one of the best, and as a bonus receive his sound advice regarding leadership.
Murray has written a book that should be on the shelf of any manager, er leader, associated with the development of software products. This is definitely a "two-thumbs-up" book.
Rating:
Summary: Wisdom and Experience
Review: Successful software projects need to be organized and managed opposite to successful companies, because of the need for creativity. This book points out the differences in crystal clarity, with very specific suggestions on what to do at each stage of moving software projects forward. Of particular interest are shortcomings of the other approaches such as waterfall, hands-off, and rapid prototyping. Details on how to use RUP (Rational Unified Process) with UML examples are provided as well.
Rating:
Summary: Wisdom and Experience
Review: Successful software projects need to be organized and managed opposite to successful companies, because of the need for creativity. This book points out the differences in crystal clarity, with very specific suggestions on what to do at each stage of moving software projects forward. Of particular interest are shortcomings of the other approaches such as waterfall, hands-off, and rapid prototyping. Details on how to use RUP (Rational Unified Process) with UML examples are provided as well.
Rating: 
Summary: A Definite Step in the Right Direction
Review: The Software Industry suffers greatly from inexperienced, underdeveloped leadership. Murray Cantor's work is an excellent step in the right direction.It still suffers from an over reliance on rehashing project management techniques.
Rating:
Summary: A Definite Step in the Right Direction
Review: The Software Industry suffers greatly from inexperienced, underdeveloped leadership. Murray Cantor's work is an excellent step in the right direction. It still suffers from an over reliance on rehashing project management techniques.
Rating:
Summary: Must read for all seeking guidance in software dev....
Review: This is the perfect read for anyone who is involved in developing software in their career or for anyone looking to improve how their company views the NEW software development paradigm. This is just the beginning to an education journey....
Rating:
Summary: Planning and limited hard work are the keys to success
Review: We all suffer from a case of TDNAH (That Does Not Apply Here), but workers in information technology seem to be the pathological case. Despite years of repeated admonitions that the only way to build successful software projects is to have a specific plan and that extensive overtime is counterproductive, many still do not listen. While most of the dot-com failures were bad ideas, there were many good ideas that were poorly planned and organized. The hours that most of the employees worked were more than what one would expect from a slave, as that seemed to be the only strategy for success that many could come up with.
Once you finally admit that you are not an exceptional member of the business section of the human race, it follows that you should look for someone with accumulated wisdom regarding how to successfully manage software projects. Cracking this book open is a good place to start, provided that quality software is truly your goal. While the advice in the book is good, it is of little use for someone more interested in exercising power and fueling their ego. This book is about being a true leader that people would listen to and follow even when choices are available. Management is about motivating people with a feather duster rather than a bullwhip and this book contains a detailed plan for the creation of competent managers who can lead the development of quality software.
Perhaps we are finally at the point where the popularity of the Dilbert cartoon will be due more to the humor rather than the accurate way it describes the work environment. Wherever we are in that trend, this is one book that is helping the push in that direction.
<< 1 >>
|
