- ホーム
- > 洋書
- > 英文書
- > Computer / General
Full Description
Results-Based Software ManagementResourcesEffective software development is no longer merely an IT concern: today, it is crucial to the entire enterprise. However, most businesspeople are not ready to make informed decisions about software initiatives. The Economics of Iterative Software Development: Steering Toward Better Business Results will prepare them. Drawing on decades of software development and business experience, the authors demonstrate how to utilize practical, economics-based techniques to plan and manage software projects for maximum return on technology investments.The authors begin by dispelling widespread myths about software costs, explaining why traditional, "engineering-based" software management introduces unacceptable inefficiencies in today's development environments. Next, they show business and technical managers how to combine the principles of economics and iterative development to achieve optimal results with limited resources. Using their techniques, readers will learn how to build systems that enable maximum business innovation and process improvement-and implement software processes that allow them to do so consistently.Highlights includeHow to repeatedly quantify the value a project is delivering and quickly adjust course as needed How to reduce software project size, complexity, and other "project killers" How to identify and eliminate software development processes that don't work How to improve development processes, reduce rework, mitigate risk, and identify inefficiencies How to create more proficient teams by improving individual skills, team interactions, and organizational capability Where to use integrated, automated tools to improve effectiveness What to measure, and when: specific metrics for project inception, elaboration, construction, and transitionThe Economics of Iterative Software Development: Steering Toward Better Business Results will help both business and technical managers make better decisions throughout the software development process-and it will help team and project leaders keep any project or initiative on track, so they can deliver more value faster.
Contents
Preface xiiiAbout the Authors xviiPart I: The Software-Driven Economy 1Chapter 1: The Challenge of Software Project Management 3The High Stakes in Software Development 4Institutional Focus 5Traditional Software ProjectManagement 7Problems with theWaterfall Approach 8Summary 11Chapter 2: Achieving Results: The Case for Software Economics 13Iterative Development 15Benefits of the Results-Based Approach 16TheMark of Success 18Summary 19Part II: Improving Software Development Economics 21Chapter 3: Trends in Software Economics 23A SimplifiedModel of Software Economics 24Software Engineering: A 40-Year History 26Keys to Improvement: A Balanced Approach 28Summary 30Chapter 4: Reducing Software Project Size or Complexity 33Managing Scope 33Reducing the Size of Human-Generated Code 35Improving Reuse Using Service-Oriented Architectures 36Summary 36Chapter 5: Improving the Development Process 39Project Processes 39Using an Iterative Process 40Attacking Significant Risks Early 43Improve Practices Incrementally to Meet Goals 46Summary 48Chapter 6: Improving Team Proficiency 51Enhancing Individual Performance 52Improving Project Teamwork 52Advancing Organizational Capability 55Summary 57Chapter 7: Improving Automation Through Integrated Tools 59Improving Human Productivity 60Eliminating Error Sources 61Enabling Process Improvements 62Summary 63Chapter 8: Accelerating Culture Change Through Common Sense 65Profiles of Successful Organizations 65Keys to Success 67Recommendation: Select the Right Project, the RightPeople, and the Right Goals 73Summary 73Part III: Practical Measurement for Software Engineering 77Chapter 9: A Practical View of Software Development Metrics 79Measurements and Goals 80Variability and Goals 80Measurement and Iterative Development 81WhenMeasurement GoesWrong 83What'sWrong with Detailed Up-front Planning? 85DecidingWhat toMeasure, Phase by Phase 86Summary 87Chapter 10: What to Measure in the Inception Phase 89Assessing Financial Viability 90Assessing Technical Viability and Estimating OverallProject Cost 91Iteration in the Inception Phase 93OtherMeasures 94Summary 96Chapter 11: What to Measure in the Elaboration and Construction Phases 99Measurement in the Elaboration Phase 99Measuring Risk Reduction 102Measuring Progress 104Measurement in the Construction Phase 106Measuring the Project Backlog 107Measuring Test Coverage 107Measuring Build Stability 108Expected Progress Trends in the Construction Phase 109Summary 110Chapter 12: What to Measure in the Transition Phase 113Measurement in the Transition Phase 114Concluding the Transition Phase 118Summary 119Chapter 13: Measuring Projects Embedded in Programs 123Organizing Projects into Programs 124Measuring Program Stages 127Summary 127Appendix: Getting Started with Iterative Project Management 129Embarking on Your First Iterative Project 130Adopting an Iterative Approach Iteratively 144Conclusion 154Suggested Reading 157Index 161
