|
Rapid Development (平装)
by Steve McConnell
| Category:
Software development, IT, Technology |
| Market price: ¥ 378.00
MSL price:
¥ 338.00
[ Shop incentives ]
|
| Stock:
Pre-order item, lead time 3-7 weeks upon payment [ COD term does not apply to pre-order items ] |
MSL rating:
 Good for Gifts |
| MSL Pointer Review:
A succinct, well organized and must-read collection of the lessons learned and best practices in software engineering over the last three decades. |
| If you want us to help you with the right titles you're looking for, or to make reading recommendations based on your needs, please contact our consultants. |
|
| |
AllReviews |
  1 2 Total 2 pages 18 items |
|
|
Jessica Sant (MSL quote), USA
<2007-01-10 00:00>
Despite the fact that this book is over 5 years old - its still an excellent resource. I used this book in my Software Project Management course for my Master's Degree and can definiltly see myself using it in the future at work.
The book clearly explains the many risks and strategies involved in Rapid Development. The author uses anecdotes and examples effectively to illustrate his points. Many of the ideas build on top of each other to reinforce good methodologies for a project manager to follow - but the book can also be read randomly (a chapter here, a chapter there).
This is a great resource from a developer's perspective too - it gives you the ammunition to debate with an untrained, unknowledgable, mis- informed or mislead project manager who's asking WAY too much and doesn't even realize it. I think anyone involved in the software engineer- ing process will be able to take away a lot of knowledge from this book. |
|
|
John Nolley (MSL quote), USA
<2007-01-10 00:00>
Those who have worked in the software industry are all too aware of the impacts of poor project planning and management endemic to their field: long hours of overtime, burnout, poor and difficult-to-revise code, etc. Even those outside the industry itself suffer from delayed product delivery, excessive bugs, and lack of product functionality due to shortcomings in project management. Rapid Development by Steve McConnell is the solution!
This isn't a book about how to program but rather how to plan to program and how to manage the tasks of development during programming. McConnell identifies some of the worst and most common mistakes made in project planning and describes their impact: ambitious deadlines cause high stress, coding errors, and usually cause the project to be completed way behind schedule; lack of communications between involved parties (users, managers, testers, developers etc.) leads to unrealistic expectations and missed goals; lack of proper planning and "coding like hell" lead to unmaintanable software, increased product bugs, etc.
Although to many software developers it may sound like McConnell is simply preaching to the choir, he offers solutions to each pitfall, many in the form of "best practices" with thorough analysis as to the appropriate use and any downsides of each. McConnell speaks from experience, having worked in development, management, and as a consultant for firms including Microsoft. Best of all, most of his solutions and practices he offers are simple to implement and pay off enormously over the lifetime of a project.
If more software companies followed the advice of McConnell's excellent book, software development might be a much more enjoyable profession, companies would save both time and money, and even the general public would be more satisfied with computer software whose headaches all too often stem from the poor development practices of the industry. |
|
|
Mike Schaefer (MSL quote), USA
<2007-01-10 00:00>
Just wanted to laugh at the folks criticizing this book because it comes from someone who worked at Microsoft. The funny thing is that, in my 10 years as a software developer, 99% of the people who complain about Microsoft sofware being buggy are themselves working on a project suffering from the same problems or worse. Let those who are free of sin cast the first stone. And since software engineering involves trying to control something that is inherently chaotic and error prone as a rule, I don't believe many of us will be casting stones. (Unless you are working on a one man project at a University or something). Keep in mind that Microsoft produces more software then anybody else out there, and given the level of sophistication, do a pretty good job. There is a group of people who deeply resent having to run MS software on their PC's because they wanted other platforms to have more of a following. I am one of those hard to find people who understand the technical limitations of much of MS software but who respects, from a business point of view, the software machine that they've become.
My recommendation to those of you without a deep seeded hatred of Microsoft (and with an ounce of open mindedness left) is this: go to a bookstore and just peruse Chapter 3 on classic mistakes. If this doesn't adequately describe the most common mistakes you've seen in your development career, then you don't need the book. |
|
|
Chris (MSL quote), USA
<2007-01-10 00:00>
For the past few years I have been working as an in house system developer for a major communications company. Recently I decided to delve into project management fundamentals because I may want to lean in that direction in the near future. Sooo... I ordered this book because of rave reviews on Amazon. Let me just say that although I haven't read through every best practice in the book's last section, this is the best book on software development I have ever read by far. I have never had the pleasure of working on a well managed project. I don't know where the company I work for gets it's software project managers but they don't seem to spend any time learning project management. This book has me on my way back to sanity and I highly recommend it. |
|
|
Teaque (MSL quote), USA
<2007-01-10 00:00>
If there is any one book that all developers and would-be project managagers should have - it's this one. Steve McConnell's writing style alone makes this an enjoyable read. Filled with tons of empirical data that is germane for any software project, this book is a tremendous resource. Having developed software professionally for over ten years now, I still find this book my favorite. Even though it was published in 1996, all of the material contained therein is still very pertinent to today's N-tier software development projects. |
|
|
Kisialiou (MSL quote), USA
<2007-01-10 00:00>
I bought this book because of the well-known name of Steve McConnell. Originally I was confused by the title that seemed to indicate another super methodology that promised heavens. No need to say that I was skeptical about it. Do not look at the title, although this book emphasizes its value for the fast paced projects, it is THE BOOK on project management as a whole. In general, the book comprises practical knowledge of generations of project managers. Do not miss your chance to get it now easy in few days what took some people's life time to learn! Amidst lots of practical examples, you will also find an exciting style and lots of must-know suggestions on small, middle and large size projects. I believe that any project manager must read this book if she/he has not done it yet. In addition to what is covered in the book, the author provides lots of links and references in case you need to explore the area in more detail. The time you will save after reading this book is worth much, much more than this book costs. |
|
|
An American reader (MSL quote), USA
<2007-01-10 00:00>
Unrealistic schedules are the bane of the software world's existance. In a world of "the quick and the dead" and "first mover advantage" achieving the unachievable seems to be a way of life in the industry. Steve McConnell takes a level headed approach at this crucial problem.
Steve looks at 3 dimensions of the problem - people, process and technology. In the spirit of haste, lots of mistakes are made. Steve then covers many of the techniques available, and identifies their impact to schedule, risk, and other factors. This isn't just a "how I learned how to do it" - it's backed up by hard research on what works, and what doesn't. Invaluable information for anyone serious about improving their ability to survive in such a hypercharged environment.
Ultimately, there is no silver bullet to this problem. Telling your project manager to read this book won't solve world peace. But carefully applying the tools and techniques listed will do you a world of good. |
|
|
An American reader (MSL quote), USA
<2007-01-10 00:00>
Rapid development is my favorite book about the software development process. This is not a formal book about a specific software process but is more a menu of tried and true best practices. McConnell devotes almost half the book to summarizing 27 best practices. For each one he documents the efficacy, risks, side-effects and tradeoffs. I've applied many of these practices as a project lead with great success. You could even start implementing some of these before you have finished reading the rest of the book. I must admit that's what I did as a project lead when I first read Rapid Development.
The case studies in Rapid Development will be familiar to almost every programmer. Sometimes the solutions seem painfully obvious to those of us who have to do the work but seeing them in print really clarifies the issues.
This is an important book for programmers, project leads and their managers. It seems like every software project these days is a Rapid Development project. The importance of this book is that it shows how to develop software with an aggressive schedule without compromising quality.
|
|
|
|
1 2 Total 2 pages 18 items |
|
|
|
|
|
|
