Professional Software Development: Shorter Schedules, Higher Quality Products, More Successful Projects, Enhanced Careers by Steve McConnell

Professional Software Development: Shorter Schedules, Higher Quality Products, More Successful Projects, Enhanced Careers Reviews

• 
  Amy Gilchrist Thorne

  I can understand why many people sound as though they were disappointed with this book. It's not a "practical" book, like Code Complete, Rapid Development, or Software Estimation, that you can immediately put into practice and improve your software's code or schedules.
  
  But whether or not you agree with McConnell's conclusions about how to "fix" software development by turning it into a profession, like engineering, medicine, or law, I think it does a good job highlighting some of the ongoing struggles in developing software and making you at least think about them.
  
  I agree that some of the solutions McConnell advocates seem overly-regimented and out-of-touch with what is currently often promoted as best-practice, namely agile development.
  
  I also understand why people might think the author seems to keep going on about best practices, but never getting to the "real content" of telling us what those best practices are. From some of his allusions to them, they seem to be those described in Part 3 of Rapid Development.
• 
  Scott

  Highly recommended. If all software developers read this book (and why not? It's pretty short and written very simply) the field would greatly benefit. McConnell fills the pages with statistics and references to supporting works. It's almost a bibliography for software development best practices. The most interesting statistics have to do with the comparisons between the top-performing software development organizations and the bottom-performing ones. The gulf yawns wide between them. It definitely makes a convincing case that we all need to look at what those top-performing organizations are doing. My only worry about this one is that it may be getting outdated. Most of the references are from the 1990s and early 2000s.
• 
  Ashkan Saeedi Mazdeh

  I read this years ago so I do not remember exact details but the general ideas of the book about software development processes and processes in general were both good and pragmatic. As always McConnel is both pragmatic and practical but still really tries to improve things. He brings data as much as he can and still does not shut down his imagination which is a hard quality to find these days.
  If you are interested in improving your company's software development practices or want to know how different fields did formalize , this is a very good book to pick up.
• 
  Brian Yamabe

  Not my favorite. I care about software development, but I don't want to be part of a formal heirarchy and over site organization.
• 
  Christophe Addinquy

  
  Ma note de lecture complète en français ici