» » Software Project Survival Guide (Developer Best Practices)

Fb2 Software Project Survival Guide (Developer Best Practices) ePub

by Steve McConnell

Category: Management and Leadership
Subcategory: Business and Work
Author: Steve McConnell
ISBN: 1572316217
ISBN13: 978-1572316218
Language: English
Publisher: Microsoft Press; 1 edition (October 25, 1997)
Pages: 306
Fb2 eBook: 1999 kb
ePub eBook: 1110 kb
Digital formats: mbr docx mobi lrf

Steve McConnell is recognized as one of the premier authors and voices in the development community.

Similar books to Software Project Survival Guide: Softw Project Surv Gde p1 (Developer Best Practices). Kindle (5th Generation). Steve McConnell is recognized as one of the premier authors and voices in the development community. He is Chief Software Engineer of Construx Software and was the lead developer of Construx Estimate and of SPC Estimate Professional, winner of Software Development magazine's Productivity Award.

Equip yourself with SOFTWARE PROJECT SURVIVAL GUIDE The organization of the book was excellent, and the end of chapter notes with practices and pitfalls, as well as copious checklists provide the non-technical.

Equip yourself with SOFTWARE PROJECT SURVIVAL GUIDE. The organization of the book was excellent, and the end of chapter notes with practices and pitfalls, as well as copious checklists provide the non-technical manager with some guideposts to understand and evaluate a mature process. It's for everyone with a stake in the outcome of a development project - and especially for those without formal software project management training. Nineteen chapters in four sections cover the concepts and strategies you need for mastering the development process, including planning, design, management, quality assurance, testing, and archiving.

Software Project Survival Guide book. Software Project Survival Guide (Pro - Best Practices). Steve McConnell is always worth reading. 1572316217 (ISBN13: 9781572316218). This book has some good stuff in it. All I would say is that, just because it says, "Constantly manage stakeholder expectations," for example, does not mean that it is easy to do, or that anyone who reads this book can actually do it.

Learn more about Steve McConnell's best-selling books like Code . A practical handbook of n practices

A comprehensive set of tips and heuristics that software developers, technical leads, and project managers can apply to create more accurate estimates. Professional Software Development. Essays about the software engineering profession. A practical handbook of n practices. After the Gold Rush (out of print).

To bring the best, most trustworthy information to every internet reader. The Great Library for all. The Internet Archive is a bargain, but we need your help. But we still need to pay for servers and staff. I know we could charge money, but then we couldn’t achieve our mission. To bring the best, most trustworthy information to every internet reader.

Software Project Survival Guide (SPSG) is responsive to the problem that many people in the software industry . Steve McConnell is an internationally recognized thought leader on software development best practices.

Software Project Survival Guide (SPSG) is responsive to the problem that many people in the software industry are thrust into positions in which they are given responsibility for the outcome of a software project but are not given any formal or informal training in how to make that happen. SPSG provides an introduction to the steps that successful software projects follow that can be read by both technical and nontechnical readers.

No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Software Project Survival Guide : how to be sure your first important project isn't your last, Steve McConnell. p. cm. Includesindex. It's for everyone with a stake in the outcome of a development project-and especially for those without formal software project management training.

Equip yourself with SOFTWARE PROJECT SURVIVAL GUIDE. It's for everyone with a stake in the outcome of a development project--and especially for those without formal software project management training. That includes top managers, executives, clients, investors, end-user representatives, project managers, and technical leads. Here you'll find guidance from the acclaimed author of the classics CODE COMPLETE and RAPID DEVELOPMENT. Steve McConnell draws on solid research and a career's worth of hard-won experience to map the surest path to your goal--what he calls "one specific approach to software development that works pretty well most of the time for most projects." Nineteen chapters in four sections cover the concepts and strategies you need for mastering the development process, including planning, design, management, quality assurance, testing, and archiving. For newcomers and seasoned project managers alike, SOFTWARE PROJECT SURVIVAL GUIDE draws on a vast store of techniques to create an elegantly simplified and reliable framework for project management success. So don't worry about wandering among complex sets of project management techniques that require years to sort out and master. SOFTWARE PROJECT SURVIVAL GUIDE goes straight to the heart of the matter to help your projects succeed. And that makes it a required addition to every professional's bookshelf.

Comments to eBook Software Project Survival Guide (Developer Best Practices)
Questanthr
In "Rapid Development," a 600-ish page treatise on software project management by the same author, Steve McConnell claims that "a book half this size would be overly general to the point of uselessness." One year later, he wrote this book, which clocks in at slightly less than half the length of Rapid Development. Coincidentally, it is overly general to the point of uselessness.

There's nothing inherently wrong with this book. It's just a mad-cap race to summarize the material already available in Rapid Development into a smaller, more streamlined, significantly less useful package. If you're going to read one book on software project management, it probably shouldn't be this one. And if you've already read a book on the topic, you won't learn anything new here.
MisTereO
I'm a one-man database development shop at a nonprofit with a shoestring budget. Without the benefit of senior level programmers, I've had to learn most of my software engineering lessons the hard way- by experience.

I picked up this book seven years into the job, which in retrospect was about seven years too late. In some respects, this book repeats lessons that that have already become obvious through experience (e.g., software testing needs to be performed separately from development). But, this lends credibility to my judgment, and provides new insights substantiated by software engineering research studies. Non-technical management and funders are responsive to the hard figures I often find myself citing from this book. For example:

1) Programmers are 2.5 times more productive in a quiet office vs. a cubicle- so, I need to be allowed to work from home

2) The most efficient programmers are 10 times more productive than the least efficient programmers- really, you would think this would be obvious, but when work needs to be contracted, the low bidder is not necessarily the best choice over the long haul

Currently faced with my most substantial and challenging programming project yet, I'm essentially using this book as a cookbook to process. Upfront I was a bit overwhelmed with the scope of the project. Having finished the book, I have a well-defined process in place, am confident this will get done, and feel I am much more articulate describing the stages of software development to management and contracted vendors. Some presumably industry-standard strategies are proving invaluable- implementing a Top Ten Risk list to ensure that major barriers are addressed upfront rather than deferred, creating specific milestones, etc.

This book (or an equivalent) should absolutely be mandatory for anyone about to take on their first major software project. It is most useful because it reads like a cookbook- guiding you through all the phases of software development, one after the other.
Onoxyleili
As a non-technical business executive tasked with running a tech-heavy organization, I had to get up to speed quickly on best practices, methodologies and approaches to development. Our organization develops the bulk of our software internally, and the Engineering team represents nearly half of the company's expense spend. McConnell's book proved invaluable in providing checklists, ideas, best practices and a solid overview of the development process. The organization of the book was excellent, and the end of chapter notes with practices and pitfalls, as well as copious checklists provide the non-technical manager with some guideposts to understand and evaluate a mature process. As noted in some other reviews, this is probably not for the "First important project", but is best applied to a relatively mature and established process and organization. A good read and a useful book.
Querlaca
This book is a strong theoretical background every software project manager should understand. The author provides deep analysis why such a big number of software projects fail. The author offers a set of reality-testing tools (software project survival test) that helps to understand chances of a project to success or to fail, from the very beginning.
An intriguing idea is that "software project need hierarchy" is essentially the same as Maslow's "human need hierarchy": human beings respond to a hierarchy of needs that involve a natural progression from lower motives to higher ones. Lower motives such as food, air and water must be satisfied before we can be motivated by the need for belongingness, love, self-esteem or self-actualization. Similar hierarchy of needs applies to software projects.
The author clearly shows that the outcome of any project depends equally on both the customer and the project team, and on the way of their communication and cooperation.
Showing the power of process and distinguishing "process" from "thrashing" and "productive work", the author doesn't decline that the people are always important.
Another cunning idea presented by the author is "The Cone of Uncertainty" which means "early in the project you can have firm cost and schedule target, or a firm feature set, but not both".
While by no doubt the first part of the book "The Survival Mind-Set" is an excellent theoretic inspection, the remaining, practical parts of the book are questionable. I'd recommend you to take them skeptically, and, before taking decisive action, getting the full picture by reading "Agile Software Development" by Alistair Cockburn to get the overview of the modern methodologies, "Extreme Programming Explained" by Kent Beck as an example of such methodoloty, "Peopleware" by Tom Demarco & Timothy Lister to make sure that the good workplace and the jelled team is a major factor, "Quality is Free" by Philip B. Crosby to understand what really the quality is and "Leadership Without Easy Answers" by Ronald A. Heifetz to assure that nothing will succeed without a leader.
Related to Software Project Survival Guide (Developer Best Practices)
Enterprise-Scale Agile Software Development (Applied Software Engineering Series) eBook
Fb2 Enterprise-Scale Agile Software Development (Applied Software Engineering Series) ePub
Agile Software Development eBook
Fb2 Agile Software Development ePub
J2EE Simplified: A Practical Guide to J2EE Project Technologies for Project Managers and Other Non-Developer Team Members eBook
Fb2 J2EE Simplified: A Practical Guide to J2EE Project Technologies for Project Managers and Other Non-Developer Team Members ePub
Painless Project Management: A Step-by-Step Guide for Planning, Executing, and Managing Projects eBook
Fb2 Painless Project Management: A Step-by-Step Guide for Planning, Executing, and Managing Projects ePub
Leadership Skills for Project Managers eBook
Fb2 Leadership Skills for Project Managers ePub
Quality Software Project Management, Two Volume Set eBook
Fb2 Quality Software Project Management, Two Volume Set ePub
Absolute Beginner's Guide to Project Management (2nd Edition) eBook
Fb2 Absolute Beginner's Guide to Project Management (2nd Edition) ePub
A Survival Guide for Project Managers eBook
Fb2 A Survival Guide for Project Managers ePub
SAS/OR 9.1 User's Guide: Project Management, Volumes 1 and 2 eBook
Fb2 SAS/OR 9.1 User's Guide: Project Management, Volumes 1 and 2 ePub