Ace the Programming Interview

Description

Cover; Copyright page; Contents at a Glance; Table of Contents; Welcome; Art vs. Science of Software Estimation; Why This Book Was Written and Who It Is For; Key Benefits Of This Book; What This Book Is Not About; Where to Start; Microsoft Press Support; Acknowledgments; Equations; Figures; Part I: Critical Estimation Concepts; Chapter 1: What Is an "Estimate"?; 1.1 Estimates, Targets, and Commitments; 1.2 Relationship Between Estimates and Plans; 1.3 Communicating about Estimates, Targets, and Commitments; 1.4 Estimates as Probability Statements; 1.5 Common Definitions of a "Good" Estimate.;Often referred to as the "black art" because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward--once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation--distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures, u. Cover Copyright page Contents at a Glance Table of Contents Welcome Art vs. Science of Software Estimation Why This Book Was Written and Who It Is For Key Benefits Of This Book What This Book Is Not About Where to Start Microsoft Press Support Acknowledgments Equations Figures Part I: Critical Estimation Concepts Chapter 1: What Is an "Estimate"? 1.1 Estimates, Targets, and Commitments 1.2 Relationship Between Estimates and Plans 1.3 Communicating about Estimates, Targets, and Commitments 1.4 Estimates as Probability Statements 1.5 Common Definitions of a "Good" Estimate. 1.6 Estimates and Project Control1.7 Estimation's Real Purpose 1.8 A Working Definition of a "Good Estimate" Additional Resources Chapter 2: How Good an Estimator Are You? 2.1 A Simple Estimation Quiz 2.2 Discussion of Quiz Results How Confident Is "90% Confident"? How Wide Should You Make Your Ranges? Where Does Pressure to Use Narrow Ranges Come From? How Representative Is This Quiz of Real Software Estimates? Chapter 3: Value of Accurate Estimates 3.1 Is It Better to Overestimate or Underestimate? Arguments Against Overestimation Arguments Against Underestimation. Weighing the Arguments3.2 Details on the Software Industry's Estimation Track Record How Late Are the Late Projects? One Company's Experience The Software Industry's Systemic Problem 3.3 Benefits of Accurate Estimates 3.4 Value of Predictability Compared with Other Desirable Project Attributes 3.5 Problems with Common Estimation Techniques Additional Resources Chapter 4: Where Does Estimation Error Come From? 4.1 Sources of Estimation Uncertainty 4.2 The Cone of Uncertainty Can You Beat the Cone? The Cone Doesn't Narrow Itself. Accounting for the Cone of Uncertainty in Software EstimatesRelationship Between the Cone of Uncertainty and Commitment The Cone of Uncertainty and Iterative Development 4.3 Chaotic Development Processes 4.4 Unstable Requirements Estimating Requirements Growth 4.5 Omitted Activities 4.6 Unfounded Optimism 4.7 Subjectivity and Bias 4.8 Off-the-Cuff Estimates 4.9 Unwarranted Precision 4.10 Other Sources of Error Additional Resources Chapter 5: Estimate Influences 5.1 Project Size Why Is This Book Discussing Size in Lines of Code? Diseconomies of Scale. When You Can Safely Ignore Diseconomies of ScaleImportance of Diseconomy of Scale in Software Estimation 5.2 Kind of Software Being Developed 5.3 Personnel Factors 5.4 Programming Language 5.5 Other Project Influences 5.6 Diseconomies of Scale Revisited Additional Resources Part II: Fundamental Estimation Techniques Chapter 6: Introduction to Estimation Techniques 6.1 Considerations in Choosing Estimation Techniques What's Being Estimated Project Size Software Development Style Development Stage Accuracy Possible 6.2 Technique Applicability Tables.