- ISBN13: 9781556159008
- Condition: NEW
- Notes: Brand New from Publisher. No Remainder Mark.
Product Description
Corporate and commercial software-development teams all want solutions for one important problem–how to get their high-pressure development schedules under control. In RAPID DEVELOPMENT, author Steve McConnell addresses that concern head-on with overall strategies, specific best practices, and valuable tips that help shrink and control development schedules and keep projects moving. Inside, you’ll find:• A rapid-development strategy that can be applied to … More >>
Rapid Development: Taming Wild Software Schedules
Tags: Development, Rapid, Schedules, Software, Taming, Wild
#1 by Anonymous on February 22, 2010 - 11:27 pm
Yes, at first read, this book seems very helpful. Seems like I can identify, etc. However, I’m sorry but I have trouble getting software development answers/advice from a team that cannot deliver product properly. Even if the answers given are the correct ones. That’s like saying 2 factorial is equal to 2 by taking 2 and adding it to zero; correct answer, wrong path.
Rating: 1 / 5
#2 by Anonymous on February 23, 2010 - 12:49 am
I recently took an online algebra tutorial and I was amazed at how well organized, clearly and simply presented, and how thoroughly I understood and retained the subject of alegbra for the very first time in my life. Whoever put that course together gets a solid A+ from me. Most teachers and instructors, including books and courses, I’ve had over the years would get an F-Minus from me, including the high school algebra teacher; The vast majority of these dismal failures should be doing something else, seriously. That goes for two gifted guys Grady Booch (Object Oriented Analysis and Design) and jeffrey Witten (Systems Analysis and Design), two books I own; both who make lousy instructors. Both books are dismal failures; more junk for the bon-fire. I wasn’t able to understand one thing they said and I retained almost nothing. Grady’s approach is bogged down with one page after another of solid rambling rhetoric. Whitten fails primarily with the chart approach; the same vague, modified chart page after page. The approach just didn’t work for either. Steve knows his subject of Project Development very well; the planning and development that must preceed any project. But I give him only a marginal grade of C for the organization, presentation, and approach of the three books I own: Project Survival Guide, Rapid Devlopment, and Code Complete. I was only able to grasp some of what he was saying, and I have had a decade of experience as a senior programmer-analyst with advanced training. The books are a little too unorganized to cement the subject. He does convey one very strong message very well: you had better prepare and plan properly before spending time and expense on system project development. I know firsthand the consequences of not heeding his advice. One company I worked for on the development staff spent many millions of dollars, years of time, and dozens of staff personnel, before outside field personnel complained that the system was way too slow. I will have to re-read Steve’s books. I give him a B+ for content and a C for instruction.
Rating: 3 / 5
#3 by Anonymous on February 23, 2010 - 3:14 am
I recently took an online algebra tutorial and I was amazed at how well organized, clearly and simply presented, and how thoroughly I understood and retained the subject of alegbra for the very first time in my life. Whoever put that course together gets a solid A+ from me. Most teachers and instructors, including books and courses, I’ve had over the years would get an F-Minus from me, including the high school algebra teacher; The vast majority of these dismal failures should be doing something else, seriously. That goes for two gifted guys Grady Booch (Object Oriented Analysis and Design) and jeffrey Witten (Systems Analysis and Design), two books I own; both who make lousy instructors. Both books are dismal failures; more junk for the bon-fire. I wasn’t able to understand one thing they said and I retained almost nothing. Grady’s approach is bogged down with one page after another of solid rambling rhetoric. Whitten fails primarily with the chart approach; the same vague, modified chart page after page. The approach just didn’t work for either. Steve knows his subject of Project Development very well; the planning and development that must preceed any project. But I give him only a marginal grade of C for the organization, presentation, and approach of the three books I own: Project Survival Guide, Rapid Devlopment, and Code Complete. I was only able to grasp some of what he was saying, and I have had a decade of experience as a senior programmer-analyst with advanced training. The books are a little too unorganized to cement the subject. He does convey one very strong message very well: you had better prepare and plan properly before spending time and expense on system project development. I know firsthand the consequences of not heeding his advice. One company I worked for on the development staff spent many millions of dollars, years of time, and dozens of staff personnel, before outside field personnel complained that the system was way too slow. I will have to re-read Steve’s books. I give him a B+ for content and a C for instruction.
Rating: 3 / 5
#4 by M. Martin on February 23, 2010 - 5:42 am
I felt really silly ordering a 10 year old computer book. But this one really is a classic and rereading it was worth the cost of admission. It is amazing how many of the lessons we have forgotten.
Rating: 3 / 5
#5 by Anonymous on February 23, 2010 - 6:08 am
200
Rating: 5 / 5